Vinod Kumar Vavilapalli commented on YARN-2517:

I am not entirely sure we need a parallel client for this. The other clients 
needed async clients because
 - they had loads of functionality that made sense in the blocking and 
non-blocking modes
 - the client code really needed call-back hooks to act on the results.

Timeline Client's only responsibility is to post events. There are only two 
use-cases: Clients need a sync write through, or 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.

What do others think?

> 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