[
https://issues.apache.org/jira/browse/YARN-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318680#comment-14318680
]
Vrushali C commented on YARN-3031:
----------------------------------
hi [~djp],
Thanks for looking at this! Yes, the calls from client (like AM) to write an
entity info could be sync ( blocking) or async (non-blocking), but the storage
writer api (TimelineServiceWriter) calls are always synchronous (blocking).
The Base Aggregator Service would provide both options of writes (sync and
async) in it's API. Would be part of YARN-3167 I think.
I have modified the sequence diagram to say that calls from AM to Base
Aggregator Service can be sync or async.
thanks
Vrushali
> [Storage abstraction] Create backing storage write interface for ATS writers
> ----------------------------------------------------------------------------
>
> Key: YARN-3031
> URL: https://issues.apache.org/jira/browse/YARN-3031
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Sangjin Lee
> Assignee: Vrushali C
> Attachments: Sequence_diagram_write_interaction.png,
> YARN-3031.01.patch
>
>
> Per design in YARN-2928, come up with the interface for the ATS writer to
> write to various backing storages. The interface should be created to capture
> the right level of abstractions so that it will enable all backing storage
> implementations to implement it efficiently.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
