[YARN-5633] Update Container Version in NMStateStore only if Resources have changed

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Assignee: Arun Suresh
• Reporter: Arun Suresh
• Created: 09/Sep/16 16:13
• Updated: 09/Sep/16 16:50
• Resolved: 09/Sep/16 16:48

Description

YARN-5221 introduced a containerVersion that is stored in the NMStateStore. The version is stored when

1. the container is first started in the NM
2. when the AM requests the NM to increase the Container resources.
3. when the RM notifies the NM to decrease the Container resources.

Unfortunately, this would result in NM not being able to rollback after an upgrade (for eg. from 2.8 > 2.7).. as noticed by jlowe.

This JIRA proposes to update the version in the NM state store only when 2 and 3 above occurs, this way, the rollback will be hampered only if the user has used the new feature (resource increase / decrease)

Issue Links

• duplicates: YARN-5630 NM fails to start after downgrade from 2.8 to 2.7