[YARN-4245] Clean up container-executor binary invocation interface

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.8.0, 3.0.0-alpha1
• Assignee: Sidharta Seethana
• Reporter: Sidharta Seethana
• Created: 09/Oct/15 07:28
• Updated: 12/May/16 18:29

Description

The current container-executor invocation interface (especially for launch container) is cumbersome to use . Launching a container now requires 13-15 arguments. This becomes especially problematic when additional, potentially optional, arguments are required. We need a better mechanism to deal with this. One such mechanism could be to handle this could be to use a file containing key/value pairs (similar to container-executor.cfg) corresponding to the arguments each invocation needs. Such a mechanism would make it easier to add new optional arguments to container-executor and better manage existing ones.

Sub-Tasks

• Generalize config file handling in container-executor: Resolved
• Change signal container invocation to use a command/config file mechanism: Open