hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6688) Store job configurations in Timeline Service v2
Date Tue, 03 May 2016 01:22:13 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15267877#comment-15267877
] 

Li Lu commented on MAPREDUCE-6688:
----------------------------------

Actually I was thinking about using the async post vs. the synced version, too. One concern
for using the blocking call is the potential size of the data we post. If the data is too
big then a blocking call may delay the job launching process. Given the fact that we're limiting
the size of each configs, I'm fine with either one but the blocking one seems to have stronger
guarantees. I agree that we need to clean up all our sync/asycn post API calls and probably
have some guidance on using them. 

Let's update the non-refactoring version and push this in. 

> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org


Mime
View raw message