[
https://issues.apache.org/jira/browse/YARN-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236763#comment-14236763
]
Tsuyoshi OZAWA commented on YARN-2517:
--------------------------------------
Thanks for your comments, [~zjshen], [~sjlee0], [~mitdesai], [~hitesh].
If we don't care communication problem, fire-and-forget approach in
putEntitiesAsync sounds reasonable to me. In this case, it's reasonable to me
to use Future without callbacks. v2 design is based on Future, so I appreciate
if you have feedbacks. One possible API to be added is flush() to assure to
send all pending requests. It can be added on separate JIRA.
> 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)
