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 "Hudson (JIRA)" <ji...@apache.org> on 2019/07/09 17:56:00 UTC
[jira] [Commented] (HDDS-1718) Increase Ratis Leader election
timeout default
[ https://issues.apache.org/jira/browse/HDDS-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881438#comment-16881438 ]
Hudson commented on HDDS-1718:
------------------------------
FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #16876 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/16876/])
HDDS-1718. Increase Ratis Leader election timeout default. Contributed (msingh: rev 96d05559132630288126d9e66a66ac31617334a4)
* (edit) hadoop-hdds/common/src/main/java/org/apache/hadoop/hdds/scm/ScmConfigKeys.java
* (edit) hadoop-hdds/common/src/main/resources/ozone-default.xml
* (edit) hadoop-hdds/container-service/src/test/java/org/apache/hadoop/ozone/container/common/statemachine/commandhandler/TestCloseContainerCommandHandler.java
> Increase Ratis Leader election timeout default
> ----------------------------------------------
>
> Key: HDDS-1718
> URL: https://issues.apache.org/jira/browse/HDDS-1718
> Project: Hadoop Distributed Data Store
> Issue Type: Task
> Components: Ozone Datanode
> Reporter: Aravindan Vijayan
> Assignee: Siddharth Wagle
> Priority: Critical
> Labels: pull-request-available
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> While testing out ozone with long running clients which continuously write data, it was noted that whenever a 1 second GC pause occurs in the leader, it triggers a leader election thereby disturbing the steady state of the system for more time than the GC pause delay.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org