[
https://issues.apache.org/jira/browse/MAPREDUCE-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268040#comment-15268040
]
Varun Saxena commented on MAPREDUCE-6688:
-----------------------------------------
bq. If the data is too big then a blocking call may delay the job launching
process.
Seems it would not. Other components interact with JobHistoryEventHandler via a
queue. JobHistoryEventHandler fetches events from this queue and then processes
them.
bq. I'm leaning slightly towards the blocking call, as the config is arguably
more important information.
Ok. Lets go with sync then. I was frankly thinking of configs to be async put
so that we carry on and process other events. But you can say better to publish
configs then not have them at all esp when we are publishing them from a single
place.
If we consider some events to be important and hence a sync, should we do a
retry on exception ? Probably the only advantage we gain right now is that they
get pushed immediately and hence would have lesser chance of not being sent on
stop or worse still not being missed on a crash.
> 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
> Affects Versions: YARN-2928
> Reporter: Junping Du
> Assignee: Varun Saxena
> Labels: yarn-2928-1st-milestone
> Attachments: MAPREDUCE-6688-YARN-2928.01.patch,
> MAPREDUCE-6688-YARN-2928.02.patch, MAPREDUCE-6688-YARN-2928.03.patch,
> MAPREDUCE-6688-YARN-2928.v2.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
