You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Hunt (Updated) (JIRA)" <ji...@apache.org> on 2012/03/20 18:13:38 UTC

[jira] [Updated] (ZOOKEEPER-1428) Create command line tool to utilize the new classes introduced in ZOOKEEPER-271

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Hunt updated ZOOKEEPER-1428:
------------------------------------

    Component/s: scripts
                 java client
         Labels: newbie  (was: )
     Issue Type: New Feature  (was: Task)

I'd love to see this available. Would be a great project for someone interested in making a positive difference for end users (and admins)!
                
> Create command line tool to utilize the new classes introduced in ZOOKEEPER-271
> -------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-1428
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1428
>             Project: ZooKeeper
>          Issue Type: New Feature
>          Components: java client, scripts
>            Reporter: Zhihong Yu
>              Labels: newbie
>
> See discussion entitled 'ZOOKEEPER-1059 Was: Does the rolling-restart.sh script work?' on zookeerper-dev
> HBase bin/rolling-restart.sh depends on zkcli returning non-zero exit code for non-existing znode.
> Jonathan Hsieh found that rolling-restart.sh no longer works using zookeeper 3.4.x
> From Patrick Hunt:
> I think what we need is to have a tool that's intended for use both
> programmatically and by humans, with more strict requirements about
> input, output formatting and command handling, etc... Please see the
> work Hartmut has been doing as part of 271 on trunk (3.5.0). Perhaps
> we can augment these new classes to also support such a tool. However
> it should instead be a true command line tool, rather than a shell.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira