symious opened a new pull request #3704:
URL: https://github.com/apache/hadoop/pull/3704


   <!--
     Thanks for sending a pull request!
       1. If this is your first time, please read our contributor guidelines: 
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
       2. Make sure your PR title starts with JIRA issue id, e.g., 
'HADOOP-17799. Your PR title ...'.
   -->
   
   ### Description of PR
   
   In HDFS-16320, the DataNode can retrieve the SLOW status from each NameNode. 
   
   This ticket is to send this information back to Clients who are writing 
blocks. If a Clients noticed the pipeline is build on a slownode, he/she can 
choose to mark the slownode as a badnode to exclude the node or rebuild a 
pipeline.
   
   In order to avoid the false positives, we added a config of "threshold", 
only clients continuously receives slownode reply from the same node will the 
node be marked as SLOW.
   
   Jira ticket: https://issues.apache.org/jira/browse/HDFS-16348
   
   ### How was this patch tested?
   
   unit test
   
   ### For code changes:
   
   - [x] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to