[
https://issues.apache.org/jira/browse/YARN-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14640784#comment-14640784
]
Li Lu commented on YARN-3949:
-----------------------------
On top of the current patch, how about have two simple write APIs wrap around
the current write function, one with guaranteed synchronous semantic while one
"maybe asynchronous"? For the HBase implementation we can enforce a flush after
a write in the synchronous version. Personally I think a synchronous write
semantics is less error pruning than requiring programmers to call flush after
a critical write.
> ensure timely flush of timeline writes
> --------------------------------------
>
> Key: YARN-3949
> URL: https://issues.apache.org/jira/browse/YARN-3949
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Affects Versions: YARN-2928
> Reporter: Sangjin Lee
> Assignee: Sangjin Lee
> Attachments: YARN-3949-YARN-2928.001.patch,
> YARN-3949-YARN-2928.002.patch, YARN-3949-YARN-2928.002.patch
>
>
> Currently flushing of timeline writes is not really handled. For example,
> {{HBaseTimelineWriterImpl}} relies on HBase's {{BufferedMutator}} to batch
> and write puts asynchronously. However, {{BufferedMutator}} may not flush
> them to HBase unless the internal buffer fills up.
> We do need a flush functionality first to ensure that data are written in a
> reasonably timely manner, and to be able to ensure some critical writes are
> done synchronously (e.g. key lifecycle events).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
