[jira] [Updated] (YARN-9084) Service Upgrade: With default readiness check, the status of upgrade is reported to be successful prematurely
[ https://issues.apache.org/jira/browse/YARN-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Yang updated YARN-9084: Target Version/s: 3.1.2, 3.3.0, 3.2.1 > Service Upgrade: With default readiness check, the status of upgrade is > reported to be successful prematurely > - > > Key: YARN-9084 > URL: https://issues.apache.org/jira/browse/YARN-9084 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Chandni Singh >Assignee: Chandni Singh >Priority: Major > Attachments: YARN-9084.001.patch, YARN-9084.002.patch > > > With YARN-9071 we do clear the IP address and Hostname from AM, NM and yarn > registry before upgrade. However it is observed that after the container is > launched again as part of reinit, the ContainerStatus received from NM has an > IP and host even though the container fails as soon as it is launched. > On Yarn Service side this results in the component instance transitioning to > READY state when it checks just the presence of IP address. -- 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
[jira] [Updated] (YARN-9084) Service Upgrade: With default readiness check, the status of upgrade is reported to be successful prematurely
[ https://issues.apache.org/jira/browse/YARN-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandni Singh updated YARN-9084: Attachment: YARN-9084.002.patch > Service Upgrade: With default readiness check, the status of upgrade is > reported to be successful prematurely > - > > Key: YARN-9084 > URL: https://issues.apache.org/jira/browse/YARN-9084 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Chandni Singh >Assignee: Chandni Singh >Priority: Major > Attachments: YARN-9084.001.patch, YARN-9084.002.patch > > > With YARN-9071 we do clear the IP address and Hostname from AM, NM and yarn > registry before upgrade. However it is observed that after the container is > launched again as part of reinit, the ContainerStatus received from NM has an > IP and host even though the container fails as soon as it is launched. > On Yarn Service side this results in the component instance transitioning to > READY state when it checks just the presence of IP address. -- 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
[jira] [Updated] (YARN-9084) Service Upgrade: With default readiness check, the status of upgrade is reported to be successful prematurely
[ https://issues.apache.org/jira/browse/YARN-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandni Singh updated YARN-9084: Attachment: YARN-9084.001.patch > Service Upgrade: With default readiness check, the status of upgrade is > reported to be successful prematurely > - > > Key: YARN-9084 > URL: https://issues.apache.org/jira/browse/YARN-9084 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Chandni Singh >Assignee: Chandni Singh >Priority: Major > Attachments: YARN-9084.001.patch > > > With YARN-9071 we do clear the IP address and Hostname from AM, NM and yarn > registry before upgrade. However it is observed that after the container is > launched again as part of reinit, the ContainerStatus received from NM has an > IP and host even though the container fails as soon as it is launched. > On Yarn Service side this results in the component instance transitioning to > READY state when it checks just the presence of IP address. -- 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
[jira] [Updated] (YARN-9084) Service Upgrade: With default readiness check, the status of upgrade is reported to be successful prematurely
[ https://issues.apache.org/jira/browse/YARN-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandni Singh updated YARN-9084: Attachment: (was: YARN-9084.001.patch) > Service Upgrade: With default readiness check, the status of upgrade is > reported to be successful prematurely > - > > Key: YARN-9084 > URL: https://issues.apache.org/jira/browse/YARN-9084 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Chandni Singh >Assignee: Chandni Singh >Priority: Major > > With YARN-9071 we do clear the IP address and Hostname from AM, NM and yarn > registry before upgrade. However it is observed that after the container is > launched again as part of reinit, the ContainerStatus received from NM has an > IP and host even though the container fails as soon as it is launched. > On Yarn Service side this results in the component instance transitioning to > READY state when it checks just the presence of IP address. -- 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
[jira] [Updated] (YARN-9084) Service Upgrade: With default readiness check, the status of upgrade is reported to be successful prematurely
[ https://issues.apache.org/jira/browse/YARN-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandni Singh updated YARN-9084: Attachment: YARN-9084.001.patch > Service Upgrade: With default readiness check, the status of upgrade is > reported to be successful prematurely > - > > Key: YARN-9084 > URL: https://issues.apache.org/jira/browse/YARN-9084 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Chandni Singh >Assignee: Chandni Singh >Priority: Major > > With YARN-9071 we do clear the IP address and Hostname from AM, NM and yarn > registry before upgrade. However it is observed that after the container is > launched again as part of reinit, the ContainerStatus received from NM has an > IP and host even though the container fails as soon as it is launched. > On Yarn Service side this results in the component instance transitioning to > READY state when it checks just the presence of IP address. -- 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
[jira] [Updated] (YARN-9084) Service Upgrade: With default readiness check, the status of upgrade is reported to be successful prematurely
[ https://issues.apache.org/jira/browse/YARN-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandni Singh updated YARN-9084: Attachment: (was: YARN-9084.001.patch) > Service Upgrade: With default readiness check, the status of upgrade is > reported to be successful prematurely > - > > Key: YARN-9084 > URL: https://issues.apache.org/jira/browse/YARN-9084 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Chandni Singh >Assignee: Chandni Singh >Priority: Major > > With YARN-9071 we do clear the IP address and Hostname from AM, NM and yarn > registry before upgrade. However it is observed that after the container is > launched again as part of reinit, the ContainerStatus received from NM has an > IP and host even though the container fails as soon as it is launched. > On Yarn Service side this results in the component instance transitioning to > READY state when it checks just the presence of IP address. -- 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
[jira] [Updated] (YARN-9084) Service Upgrade: With default readiness check, the status of upgrade is reported to be successful prematurely
[ https://issues.apache.org/jira/browse/YARN-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandni Singh updated YARN-9084: Attachment: YARN-9084.001.patch > Service Upgrade: With default readiness check, the status of upgrade is > reported to be successful prematurely > - > > Key: YARN-9084 > URL: https://issues.apache.org/jira/browse/YARN-9084 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Chandni Singh >Assignee: Chandni Singh >Priority: Major > Attachments: YARN-9084.001.patch > > > With YARN-9071 we do clear the IP address and Hostname from AM, NM and yarn > registry before upgrade. However it is observed that after the container is > launched again as part of reinit, the ContainerStatus received from NM has an > IP and host even though the container fails as soon as it is launched. > On Yarn Service side this results in the component instance transitioning to > READY state when it checks just the presence of IP address. -- 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
[jira] [Updated] (YARN-9084) Service Upgrade: With default readiness check, the status of upgrade is reported to be successful prematurely
[ https://issues.apache.org/jira/browse/YARN-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandni Singh updated YARN-9084: Description: With YARN-9071 we do clear the IP address and Hostname from AM, NM and yarn registry before upgrade. However it is observed that after the container is launched again as part of reinit, the ContainerStatus received from NM has an IP and host even though the container fails as soon as it is launched. On Yarn Service side this results in the component instance transitioning to READY state when it checks just the presence of IP address. > Service Upgrade: With default readiness check, the status of upgrade is > reported to be successful prematurely > - > > Key: YARN-9084 > URL: https://issues.apache.org/jira/browse/YARN-9084 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Chandni Singh >Assignee: Chandni Singh >Priority: Major > > With YARN-9071 we do clear the IP address and Hostname from AM, NM and yarn > registry before upgrade. However it is observed that after the container is > launched again as part of reinit, the ContainerStatus received from NM has an > IP and host even though the container fails as soon as it is launched. > On Yarn Service side this results in the component instance transitioning to > READY state when it checks just the presence of IP address. -- 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
[jira] [Updated] (YARN-9084) Service Upgrade: With default readiness check, the status of upgrade is reported to be successful prematurely
[ https://issues.apache.org/jira/browse/YARN-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandni Singh updated YARN-9084: Description: This seems to be happening > Service Upgrade: With default readiness check, the status of upgrade is > reported to be successful prematurely > - > > Key: YARN-9084 > URL: https://issues.apache.org/jira/browse/YARN-9084 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Chandni Singh >Assignee: Chandni Singh >Priority: Major > > This seems to be happening -- 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
[jira] [Updated] (YARN-9084) Service Upgrade: With default readiness check, the status of upgrade is reported to be successful prematurely
[ https://issues.apache.org/jira/browse/YARN-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandni Singh updated YARN-9084: Description: (was: This seems to be happening ) > Service Upgrade: With default readiness check, the status of upgrade is > reported to be successful prematurely > - > > Key: YARN-9084 > URL: https://issues.apache.org/jira/browse/YARN-9084 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Chandni Singh >Assignee: Chandni Singh >Priority: Major > -- 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
