[
https://issues.apache.org/jira/browse/YARN-5986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15735826#comment-15735826
]
Miklos Szegedi commented on YARN-5986:
--------------------------------------
Thank you for the comment [~sjlee0]! No, I am talking only about entries for
the node manager about specific features with application scope. As of today,
YARN-5600 is the only candidate, maybe YARN-5987. We can probably make a rule
that we need to specify these only to enable rare features. The defaults apply
in most of the cases to reduce network bandwidth.
> Adding YARN configuration entries to ContainerLaunchContext
> -----------------------------------------------------------
>
> Key: YARN-5986
> URL: https://issues.apache.org/jira/browse/YARN-5986
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Miklos Szegedi
> Assignee: Miklos Szegedi
>
> Currently ContainerLaunchContext is defined as
> message ContainerLaunchContextProto {
> repeated StringLocalResourceMapProto localResources = 1;
> optional bytes tokens = 2;
> repeated StringBytesMapProto service_data = 3;
> repeated StringStringMapProto environment = 4;
> repeated string command = 5;
> repeated ApplicationACLMapProto application_ACLs = 6;
> optional ContainerRetryContextProto container_retry_context = 7;
> }
> It would be nice to have an additional parameter "configuration" to support
> cases like YARN-5600, where we want to pass a parameter to Yarn and not the
> application or container.
> repeated StringStringMapProto configuration = 8;
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
