[YARN-3684] Change ContainerExecutor's primary lifecycle methods to use a more extensible mechanism for passing information.

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8.0, 3.0.0-alpha1
• Component/s: yarn
• Hadoop Flags: Reviewed
• Release Note: Modifying key methods in ContainerExecutor to use context objects instead of an argument list. This is more extensible and less brittle.
• Assignee: Sidharta Seethana
• Reporter: Sidharta Seethana
• Created: 19/May/15 21:30
• Updated: 30/Aug/16 01:22
• Resolved: 21/May/15 22:51

Description

As per description in parent JIRA : Adding additional arguments to key ContainerExecutor methods ( e.g startLocalizer or launchContainer ) would break the existing ContainerExecutor interface and would require changes to all executor implementations in YARN. In order to make this interface less brittle in the future, it would make sense to encapsulate arguments in some kind of a ‘context’ object which could be modified/extended without breaking the ContainerExecutor interface in the future.

Issue Links

• breaks: YARN-4643 Container recovery is broken with delegating container runtime