[
https://issues.apache.org/jira/browse/YARN-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15263082#comment-15263082
]
Li Lu commented on YARN-3959:
-----------------------------
Hi [~varun_saxena], thanks for the prompt work! Some of my comments:
- Are we posting configurations for all YARN applications, or we just do that
for MapReduce apps? Actually, if we have system level support to post configs
for all YARN applications, we do not need to change much on the MR side, right?
I think configs are very general for YARN apps, so maybe we can fix that on
YARN's level rather than MR level?
- I would argue that a "size limiter" is almost a must for this feature, since
configs may get abused on some clusters (and people may not even realize that).
Of course the default payload size is fine, but something could be very wrong
if those configs are too big. We may want to have a two level limit for storing
configs: for each config we limit its max length, and we also limit the maximum
number of configs we can attach to one timeline entity. We can make these two
limits configurable on the YARN level.
If we generalize this patch to YARN level (as the title), we no longer need to
rely on MAPREDUCE-6424 for the fix. Thoughts?
> Store application related configurations in Timeline Service v2
> ---------------------------------------------------------------
>
> Key: YARN-3959
> URL: https://issues.apache.org/jira/browse/YARN-3959
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Junping Du
> Assignee: Varun Saxena
> Labels: yarn-2928-1st-milestone
> Attachments: YARN-3959-YARN-2928.01.patch
>
>
> We already have configuration field in HBase schema for application entity.
> We need to make sure AM write it out when it get launched.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
