[
https://issues.apache.org/jira/browse/HDFS-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486767#comment-13486767
]
Damien Hardy commented on HDFS-4101:
------------------------------------
I tried something like that but as an non java developer (usually sysadmin)
wasn't able to do it confronting the 'Call to super must be first statement in
constructor' ERROR
Because I want to test the constructor method ...
I can't find any workaround instead of adding a new constructor with a
parameter for number of ZK Fails which is a non-sens :)
So I tried using the available parameters ...
Maybe you can help ?
> ZKFC should implement zookeeper.recovery.retry like HBase to connect to
> ZooKeeper
> ---------------------------------------------------------------------------------
>
> Key: HDFS-4101
> URL: https://issues.apache.org/jira/browse/HDFS-4101
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: auto-failover, ha
> Affects Versions: 2.0.0-alpha, 3.0.0
> Environment: running CDH4.1.1
> Reporter: Damien Hardy
> Assignee: Damien Hardy
> Priority: Minor
> Labels: newbie
> Attachments: HDFS-4101-2.patch
>
>
> When zkfc start and zookeeper is not yet started ZKFC fails and stop directly.
> Maybe ZKFC should allow some retries on Zookeeper services like does HBase
> with zookeeper.recovery.retry
> This particularly appends when I start my whole cluster on VirtualBox for
> example (every components nearly at the same time) ZKFC is the only that fail
> and stop ...
> Every others can wait each-others some time independently of the start order
> like NameNode/DataNode/JournalNode/Zookeeper/HBaseMaster/HBaseRS so that the
> system can be set and stable in few seconds
--
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
