[
https://issues.apache.org/jira/browse/HDFS-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630800#comment-15630800
]
Andres Perez commented on HDFS-4101:
------------------------------------
I think this issue can be approached the same way YARN-4243 did it.
In HADOOP-13781 I implemented a patch using the same logic to make ZKFC to not
fail in the first try
> 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-alpha1
> Environment: running CDH4.1.1
> Reporter: Damien Hardy
> Assignee: Damien Hardy
> Priority: Minor
> Labels: BB2015-05-TBR, 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 was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
