Tsuyoshi OZAWA commented on YARN-2517:

Thanks for your comment, Vinod.

an asynchronous write, the end of which they don't care about. I think we 
should simply have a mode in the existing client to post events asynchronously 
without any further need for call-back handlers.

Make sense. We can assure at-most-once semantics without any callbacks. How 
about adding a {{flush()}} API to TimelineClient for asynchronous mode? It 
helps users to know whether contents of current buffer are written to Timeline 
Server or not.

> 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
> 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

Reply via email to