[
https://issues.apache.org/jira/browse/MAPREDUCE-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264842#comment-15264842
]
Sangjin Lee commented on MAPREDUCE-6688:
----------------------------------------
bq. If we have done something in hRaven, we can probably adopt the same
approach if conflicting opinions do not exist.
cc [~vrushalic] and [~jrottinghuis]
bq. Maybe we can go ahead with splitting with a fixed static constant for size
of configs to be sent in one shot ? Is 100 kb fine ? Thoughts ?
I'm +1 on doing multiple {{putEntities()}} calls with the upper bound of 100 KB
with one exception; if a single value exceeds that size. We just need to decide
on a behavior, and I would lean towards still sending it for now if a single
key/value exceeds the upper bound. Would it be feasible?
> 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: 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
