Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Mon, 22 Oct 2012 11:08:11 +0000 (UTC)
From: "Damien Hardy (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <438726939.9355.1350904091942.JavaMail.jiratomcat@arcas>
Subject: [jira] [Created] (HDFS-4101) ZKFC should implement
 zookeeper.recovery.retry like Hbase to connect to zookeeper
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Damien Hardy created HDFS-4101:
----------------------------------

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

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