[
https://issues.apache.org/jira/browse/YARN-8665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621108#comment-16621108
]
Chandni Singh commented on YARN-8665:
-------------------------------------
[~eyang] Thanks for the review
{quote}
Instances at READY/FAILED_UPGRADE state should be marked for NEEDS_UPGRADE, and
instances at NEEDS_UPGRADE state should be reset to RUNNING_BUT_NOT_READY to
revert the process.
{quote}
In my second patch I will fix the issue that if the instance was not upgraded
yet, cancellation will not be triggered for it as well and it will immediately
go back to READY state.
Otherwise there will be race conditions when the component reads the state of
the container and then updates it to a new state based on a condition.
> Yarn Service Upgrade: Support cancelling upgrade
> -------------------------------------------------
>
> Key: YARN-8665
> URL: https://issues.apache.org/jira/browse/YARN-8665
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Chandni Singh
> Assignee: Chandni Singh
> Priority: Major
> Attachments: YARN-8665.001.patch
>
>
> When a service is upgraded without auto-finalization or express upgrade, then
> the upgrade can be cancelled. This provides the user ability to test upgrade
> of a single instance and if that doesn't go well, they get a chance to cancel
> it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
