You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Damien Hardy (JIRA)" <ji...@apache.org> on 2012/10/22 13:10:12 UTC
[jira] [Updated] (HDFS-4101) ZKFC should implement
zookeeper.recovery.retry like Hbase to connect to zookeeper
[ https://issues.apache.org/jira/browse/HDFS-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Damien Hardy updated HDFS-4101:
-------------------------------
Description:
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
was:
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 append 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
> 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
> Priority: Minor
>
> 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