[
https://issues.apache.org/jira/browse/MAPREDUCE-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15265759#comment-15265759
]
Varun Saxena commented on MAPREDUCE-6688:
-----------------------------------------
Well I was of the opinion that right now, we are not quite sure of the approach
we might take in YARN-3401 and the solution would emerge more from the security
model we decide upon. Which we haven't given a great deal of thought on. It is
hence, possible we later decide that we will not push events from
JobHistoryEventHandler from RM, that is, if we even decide to route it via RM.
And yes, that may involve further refactoring.
So I was of the opinion let us first go with what is best for current code and
then refactor later, if required, based on decision taken. Thoughts ?
For me, there will be certain events which would require to be pushed
immediately and for that we will have a sync call(for instance, JOB_FINISHED)
and others will be async calls. So that should be clean enough. Correct ? Or
you are thinking of some other parameters on which we will make this decision ?
> 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,
> 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
