hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-11296) Maintenance state expiry should be an epoch time and not jvm monotonic
Date Fri, 20 Jan 2017 07:13:26 GMT

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

Hudson commented on HDFS-11296:

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11153 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/11153/])
HDFS-11296. Maintenance state expiry should be an epoch time and not jvm (mingma: rev f3fb94be05a61a4c4c06ab279897e5de2b181b0e)
* (edit) hadoop-hdfs-project/hadoop-hdfs-client/src/main/java/org/apache/hadoop/hdfs/protocol/DatanodeInfo.java
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestNameNodeMXBean.java
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestMaintenanceState.java

> Maintenance state expiry should be an epoch time and not jvm monotonic
> ----------------------------------------------------------------------
>                 Key: HDFS-11296
>                 URL: https://issues.apache.org/jira/browse/HDFS-11296
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>    Affects Versions: 3.0.0-alpha1
>            Reporter: Manoj Govindassamy
>            Assignee: Manoj Govindassamy
>             Fix For: 2.9.0, 3.0.0-alpha3
>         Attachments: HDFS-11296.01.patch, HDFS-11296.02.patch, HDFS-11296.03.patch, HDFS-11296-branch-2.01.patch,
HDFS-11296-branch-2.02.patch, HDFS-11296-branch-2.03.patch
> Currently it is possible to configure an expiry time in milliseconds for a DataNode in
maintenance state. As per the design, the expiry attribute is an absolute time, beyond which
NameNode starts to stop the ongoing maintenance operation for that DataNode. Internally in
the code, this expiry time is read and checked against {{Time.monotonicNow()}} making the
expiry based on more of JVM's runtime, which is very difficult to configure for any external
user. The goal is to make the expiry time an absolute epoch time, so that its easy to configure
for external users.
> {noformat}
> {
>     "hostName": <host>,
>     "port": <port>,
>     "adminState": "IN_MAINTENANCE",
>     "maintenanceExpireTimeInMS": <time in millis>
> }
> {noformat}
> DatanodeInfo.java
> {noformat}
>   public static boolean maintenanceNotExpired(long maintenanceExpireTimeInMS) {
>     return Time.monotonicNow() < maintenanceExpireTimeInMS;
>   }
> {noformat}

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