[
https://issues.apache.org/jira/browse/TEZ-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303916#comment-14303916
]
Siddharth Seth commented on TEZ-1233:
-------------------------------------
I think Vertex specific configs should only be supported via a programmatic API
(or when we have support for an external representation of a DAG). Trying to
ask users to use vertex names / indices is really not going to work very well.
With container re-use - things like the heartbeat interval etc do become an
issue. I'm not sure we should support overriding these at a DAG or Vertex level
within a session.
There are other configs, however, like number of allowed attempts for a vertex,
and additional parameters that will be required in TEZ-2003 that can be
overridden at a vertex level.
In terms of DAG configs, and isolation - that's also required. Also in parts
for TEZ-2003.
[~zjffdu] - please feel free to take over the jira.
> Allow configuration of framework parameters per vertex
> ------------------------------------------------------
>
> Key: TEZ-1233
> URL: https://issues.apache.org/jira/browse/TEZ-1233
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
>
> Currently, configuration properties specific in AMConfiguration are used to
> configure tasks - e.g. memory configs, process tree, etc. These should be
> configurable at a Vertex level.
> Also, tasks end up reading these configs from the dist cache each time -
> would be simpler to send over the wire as part of the TaskSpec.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
