[
https://issues.apache.org/jira/browse/YARN-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kartheek muthyala updated YARN-7240:
------------------------------------
Attachment: YARN-7240.002.patch
[~asuresh], Thank you for the quick feedback.
The updated patch has the following changes
1. New testcases for TestContainerSchdedulerQueuing for the paused and promoted
containers which checks the container states and their events flow through
listener class.
2. Requeing the containers to the front of the queuedGuaranteed or
queuedOpprotunistic queues would require to change the datastructures or we
have to put use some temporary auxiliary queues to move this element. I am not
sure if it can be optimal. Let me know what you think.
3. Removed the TODO comment.
> Add more states and transitions to stabilize the NM Container state machine
> ---------------------------------------------------------------------------
>
> Key: YARN-7240
> URL: https://issues.apache.org/jira/browse/YARN-7240
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Arun Suresh
> Assignee: kartheek muthyala
> Attachments: YARN-7240.001.patch, YARN-7240.002.patch
>
>
> There seem to be a few intermediate states that can be added to improve the
> stability of the NM container state machine.
> For. eg:
> * The REINITIALIZING should probably be split into REINITIALIZING and
> REINITIALIZING_AWAITING_KILL.
> * Container updates are currently handled in the ContainerScheduler, but it
> would probably be better to have it plumbed through the container state
> machine as a new state, say UPDATING and a new container event.
> The plan is to add some extra tests too to try and test every transition.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
