[
https://issues.apache.org/jira/browse/HDFS-3912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470486#comment-13470486
]
Suresh Srinivas commented on HDFS-3912:
---------------------------------------
bq. I think we should not have a warning if we're below the default, because:
I think we should have a warning because some one could set this to way smaller
value than what even HBase could be setup with. That said, we could print the
warning if the stale period is, say, 3 times the hearbeat period. Also we need
to also document in the hdfs-default.xml the pros and cons of the stale period
choices.
> Detecting and avoiding stale datanodes for writing
> --------------------------------------------------
>
> Key: HDFS-3912
> URL: https://issues.apache.org/jira/browse/HDFS-3912
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Affects Versions: 3.0.0
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Attachments: HDFS-3912.001.patch, HDFS-3912.002.patch,
> HDFS-3912.003.patch, HDFS-3912.004.patch, HDFS-3912.005.patch,
> HDFS-3912.006.patch, HDFS-3912.007.patch, HDFS-3912.008.patch
>
>
> 1. Make stale timeout adaptive to the number of nodes marked stale in the
> cluster.
> 2. Consider having a separate configuration for write skipping the stale
> nodes.
--
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
