[
https://issues.apache.org/jira/browse/YARN-7939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16451518#comment-16451518
]
Chandni Singh commented on YARN-7939:
-------------------------------------
[~eyang] you are correct. There is existing AM transition logic which gets
triggered after a component stops Flexing and changes service state to STABLE.
It doesn't take into account if the component is Upgrading. I need to fix this.
{quote}Additional error check logic is recommended to prevent user from calling
component instance upgrade when service upgrade has not been triggered.
{quote}
I don't understand what you mean by this. We throw a message that service
upgrade has not been initiated. Even in your case, though the service
incorrectly transitioned to {{STABLE}} state, you saw the message:
{code:java}
{"diagnostics":"The upgrade of service abc has not been initiated."}
{code}
> Yarn Service Upgrade: add support to upgrade a component instance
> ------------------------------------------------------------------
>
> Key: YARN-7939
> URL: https://issues.apache.org/jira/browse/YARN-7939
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Chandni Singh
> Assignee: Chandni Singh
> Priority: Major
> Attachments: YARN-7939.001.patch, YARN-7939.002.patch,
> YARN-7939.003.patch, YARN-7939.004.patch, YARN-7939.005.patch,
> YARN-7939.006.patch, YARN-7939.007.patch, YARN-7939.008.patch,
> YARN-7939.009.patch, YARN-7939.010.patch, serviceam.log, upgrade_logs.tgz
>
>
> Yarn core supports in-place upgrade of containers. A yarn service can
> leverage that to provide in-place upgrade of component instances. Please see
> YARN-7512 for details.
> Will add support to upgrade a single component instance first and then
> iteratively add other APIs and features.
>
--
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
