[
https://issues.apache.org/jira/browse/TEZ-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14313741#comment-14313741
]
Bikas Saha commented on TEZ-1233:
---------------------------------
For TEZ-1788, it is probably not sufficient to specify vertex specific disable
in code. Sometimes it may be possible to know that a vertex is
non-deterministic (e.g.) and so speculation should not be done. The disabling
would likely be necessary in an operational situation where speculation is
being unnecessarily triggered. In general, configuration is used to allow the
same job to run differently based on different conditions. So enabling
something like this that requires changing code to apply configuration is kind
of inconsistent with the concept of configuration. While its probably fine to
allow programmatic access, it seems incomplete without allowing configuration
to be changed via configuration files.
>From the above comments, it wasn't clear how this relates to TEZ-2003. Any
>light on that aspect would be helpful to understand if the code being built
>here is useful in that regard.
> 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: Jeff Zhang
> Attachments: TEZ-1233-1.patch, TEZ-1233-2.patch, TEZ-1233-3.patch
>
>
> 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)
