You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Tsuyoshi OZAWA (JIRA)" <ji...@apache.org> on 2014/11/20 17:25:35 UTC

[jira] [Updated] (YARN-2517) Implement TimelineClientAsync

     [ https://issues.apache.org/jira/browse/YARN-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tsuyoshi OZAWA updated YARN-2517:
---------------------------------
    Attachment: YARN-2517.2.patch

Sorry for the delay. Attached Future-based implementation for simplicity. I think this design is one of the best way we go to.

[~vinodkv], [~zjshen], should we add read APIs on another JIRA? And, do you have any opinions about Future-based design?



> Implement TimelineClientAsync
> -----------------------------
>
>                 Key: YARN-2517
>                 URL: https://issues.apache.org/jira/browse/YARN-2517
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Zhijie Shen
>            Assignee: Tsuyoshi OZAWA
>         Attachments: YARN-2517.1.patch, YARN-2517.2.patch
>
>
> In some scenarios, we'd like to put timeline entities in another thread no to block the current one.
> It's good to have a TimelineClientAsync like AMRMClientAsync and NMClientAsync. It can buffer entities, put them in a separate thread, and have callback to handle the responses.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)