[
https://issues.apache.org/jira/browse/MAPREDUCE-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15265651#comment-15265651
]
Varun Saxena commented on MAPREDUCE-6688:
-----------------------------------------
[~sjlee0], I think we can just take a call on what the optimum value size can
be(while keeping in mind that 10 async entities go together) as code has
already been written for it. Breaking up entities this way should work for 1st
milestone atleast.
If people have divergent views on the issue, we can raise a new JIRA to address
those issue later, say make it configurable or handle it differently.
Also I would like [~gtCarrera9] to have a look as well because he suggested
refactoring on MAPREDUCE-6424 and I have taken care of that in this JIRA.
> Store job configurations in Timeline Service v2
> -----------------------------------------------
>
> Key: MAPREDUCE-6688
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6688
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: applicationmaster
> Reporter: Junping Du
> Assignee: Varun Saxena
> Labels: yarn-2928-1st-milestone
> Attachments: MAPREDUCE-6688-YARN-2928.01.patch,
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
