[
https://issues.apache.org/jira/browse/ZOOKEEPER-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13914004#comment-13914004
]
Takashi Ohnishi commented on ZOOKEEPER-1871:
--------------------------------------------
Hmm. 1core test was failed.
But, former patch succeeded it and I made a slight change of discarding unused
local variable...
Looking the error messages, this fail seems to be related ZOOKEEPER-1870,
maybe.
{core}
junit.framework.AssertionFailedError: client could not connect to reestablished
quorum: giving up after 30+ seconds.
at
org.apache.zookeeper.test.ReconfigTest.testNormalOperation(ReconfigTest.java:153)
at
org.apache.zookeeper.server.quorum.StandaloneDisabledTest.startSingleServerTest(StandaloneDisabledTest.java:75)
at
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:52)
{core}
> Add an option to zkCli to wait for connection before executing commands
> -----------------------------------------------------------------------
>
> Key: ZOOKEEPER-1871
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1871
> Project: ZooKeeper
> Issue Type: Improvement
> Affects Versions: 3.4.5
> Reporter: Vinayakumar B
> Assignee: Takashi Ohnishi
> Attachments: ZOOKEEPER-1871.patch, ZOOKEEPER-1871.patch,
> ZOOKEEPER-1871.patch, ZOOKEEPER-1871.patch
>
>
> Add an option to zkCli to wait for connection before executing any commands.
> This is helpful for the execution of inline commands.
> We are having some scripts to create/delete znodes through commandline. But
> if getting the connection delays due to one of the node down, then command
> will fail with connectionloss even though quorum is available.
> So I propose a commandline option (similar to -server and -timeout)
> "-waitforconnection" to wait for the connection before executing any commands.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
