abhishekd0907 opened a new pull request, #5905:
URL: https://github.com/apache/hadoop/pull/5905

   
   Open Source JIRA: https://issues.apache.org/jira/browse/YARN-11421
   
   <!--
     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
   During Graceful Decommission, a Node gets deactivated before timeout even 
though there are launched containers on that node.
   
   We have observed cases when graceful decommission signal is sent to node and 
Containers are launched at NodeManager and at the same time, in such cases 
ResourceManager moves the node from Decommissioning to Decommissioned state 
because launced containers are not checked in DecommissioningNodesWatcher.
   
   We will suggest waiting for 
yarn.resourcemanager.decommissioning-nodes-watcher.delay-ms to complete before 
marking node ready to be decommissioned. No delay if set to 0. Expire interval 
should not be configured more than RM_AM_EXPIRY_INTERVAL_MS.
   
   
   ### How was this patch tested?
   Unit Tests Added 
   
   ### 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