hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-4101) ZKFC should implement zookeeper.recovery.retry like HBase to connect to ZooKeeper
Date Wed, 06 May 2015 03:37:45 GMT

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

Allen Wittenauer updated HDFS-4101:
-----------------------------------
    Labels: BB2015-05-TBR newbie  (was: newbie)

> 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: 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)

Mime
View raw message