Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 30 May 2012 19:56:23 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <57312913.17983.1338407783578.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <986385142.5377.1338015323327.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HDFS-3468) Make BKJM-ZK session timeout
 configurable.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285964#comment-13285964 ] 

Hudson commented on HDFS-3468:
------------------------------

Integrated in Hadoop-Common-trunk-Commit #2303 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2303/])
    HDFS-3468. Make BKJM-ZK session timeout configurable. Contributed by Uma Maheswara Rao G. (Revision 1344423)

     Result = SUCCESS
umamahesh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1344423
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/contrib/bkjournal/src/main/java/org/apache/hadoop/contrib/bkjournal/BookKeeperJournalManager.java

                
> Make BKJM-ZK session timeout configurable.
> ------------------------------------------
>
>                 Key: HDFS-3468
>                 URL: https://issues.apache.org/jira/browse/HDFS-3468
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>    Affects Versions: 2.0.0-alpha
>            Reporter: Uma Maheswara Rao G
>            Assignee: Uma Maheswara Rao G
>             Fix For: 2.0.1-alpha
>
>         Attachments: HDFS-3468.patch
>
>
> Currently BKJM-ZK session timeout has been hardcoded to 3000ms.
> Considering ZKFC timeouts configurable, we should make this also configurable.
> Unfortunale we can not compare both the values at runtime, because they both are different processes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira