[
https://issues.apache.org/jira/browse/GIRAPH-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454241#comment-13454241
]
Eli Reisman commented on GIRAPH-312:
------------------------------------
Unless its gone stale (should be OK) this is working, tested on 2 clusters, and
passes mvn verify (etc.) so I think we're ready for review here.
> Giraph needs an admin script
> ----------------------------
>
> Key: GIRAPH-312
> URL: https://issues.apache.org/jira/browse/GIRAPH-312
> Project: Giraph
> Issue Type: New Feature
> Components: conf and scripts, zookeeper
> Affects Versions: 0.2.0
> Reporter: Eli Reisman
> Assignee: Eli Reisman
> Priority: Minor
> Fix For: 0.2.0
>
> Attachments: GIRAPH-312-1.patch, GIRAPH-312-2.patch,
> GIRAPH-312-3.patch, GIRAPH-312-3.patch, GIRAPH-312-4.patch, GIRAPH-312-5.patch
>
>
> Our zookeeper instances have very long uptimes on our cluster, and failed job
> trees are never cleaned from memory. There is a separate shell script to do
> this, but its not picky about which node trees it erases, and on some systems
> some Giraph users may not have access to it.
> This patch will add a shell script to activate a new class which will use
> Giraph conf file options or our normal -Dgiraph.XYZ command-line opts to get
> the ZK quorum info, and clean out the remnants from its memory of old failed
> and killed jobs. They do pile up over time.
> This led to the larger idea that Giraph needs a general giraph-admin shell
> script as a home for stuff like this. Jakob suggested it would be a good idea
> to put this into such a script since then admin groups can be created so that
> not every Giraph client can run it. This script currently only has code to
> start up the zk cleaner, but can have more options added to it as JIRA's to
> add features crop up.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
