[ https://issues.apache.org/jira/browse/HDFS-13949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nanda kumar updated HDFS-13949: ------------------------------- Status: Patch Available (was: Open) > Correct the description of dfs.datanode.disk.check.timeout in hdfs-default.xml > ------------------------------------------------------------------------------ > > Key: HDFS-13949 > URL: https://issues.apache.org/jira/browse/HDFS-13949 > Project: Hadoop HDFS > Issue Type: Bug > Components: documentation > Reporter: Toshihiro Suzuki > Assignee: Toshihiro Suzuki > Priority: Minor > Attachments: HDFS-13949.1.patch > > > The description of dfs.datanode.disk.check.timeout in hdfs-default.xml is as > follows: > {code} > <property> > <name>dfs.datanode.disk.check.timeout</name> > <value>10m</value> > <description> > Maximum allowed time for a disk check to complete during DataNode > startup. If the check does not complete within this time interval > then the disk is declared as failed. This setting supports > multiple time unit suffixes as described in dfs.heartbeat.interval. > If no suffix is specified then milliseconds is assumed. > </description> > </property> > {code} > I don't think the value of this config is used only during DataNode startup. > I think it's used whenever checking volumes. > The description is misleading so we need to correct it. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org