[
https://issues.apache.org/jira/browse/HDFS-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498217#comment-13498217
]
Hudson commented on HDFS-3623:
------------------------------
Integrated in Hadoop-trunk-Commit #3026 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/3026/])
HDFS-3623. BKJM: zkLatchWaitTimeout hard coded to 6000. Make use of
ZKSessionTimeout instead. Contributed by Uma Maheswara Rao G. (Revision 1409905)
Result = SUCCESS
umamahesh :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1409905
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/contrib/bkjournal/src/main/java/org/apache/hadoop/contrib/bkjournal/BookKeeperJournalManager.java
> BKJM: zkLatchWaitTimeout hard coded to 6000. Make use of ZKSessionTimeout
> instead.
> ----------------------------------------------------------------------------------
>
> Key: HDFS-3623
> URL: https://issues.apache.org/jira/browse/HDFS-3623
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: name-node
> Affects Versions: 2.0.0-alpha
> Reporter: Uma Maheswara Rao G
> Assignee: Uma Maheswara Rao G
> Fix For: 3.0.0, 2.0.3-alpha
>
> Attachments: HDFS-3623.patch, HDFS-3628.patch
>
>
> {code}
> if (!zkConnectLatch.await(6000, TimeUnit.MILLISECONDS)) {
> {code}
> we can make use of session timeout instead of hardcoding this value.
--
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
