hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anu Engineer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-11740) Ozone: Differentiate time interval for different DatanodeStateMachine state tasks
Date Thu, 04 May 2017 18:28:04 GMT

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

Anu Engineer commented on HDFS-11740:

makes sense, let us revisit this later. I am sure as we add more states we will have a better
handle on this issue. Thanks for your work and discussion around this JIRA.

> Ozone: Differentiate time interval for different DatanodeStateMachine state tasks
> ---------------------------------------------------------------------------------
>                 Key: HDFS-11740
>                 URL: https://issues.apache.org/jira/browse/HDFS-11740
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ozone
>            Reporter: Weiwei Yang
>            Assignee: Weiwei Yang
>         Attachments: HDFS-11740-HDFS-7240.001.patch, HDFS-11740-HDFS-7240.002.patch,
HDFS-11740-HDFS-7240.003.patch, statemachine_1.png, statemachine_2.png
> Currently datanode state machine transitioned between tasks in a fixed time interval,
defined by {{ScmConfigKeys#OZONE_SCM_HEARTBEAT_INTERVAL_SECONDS}}, the default value is 30s.
Once datanode is started, it will need 90s before transited to {{Heartbeat}} state, such a
long lag is not necessary. Propose to improve the logic of time interval handling, it seems
only the heartbeat task needs to be scheduled in {{OZONE_SCM_HEARTBEAT_INTERVAL_SECONDS}}
interval, rest should be done without any lagging.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message