hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3949) ensure timely flush of timeline writes
Date Fri, 24 Jul 2015 19:01:05 GMT

    [ https://issues.apache.org/jira/browse/YARN-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14640935#comment-14640935
] 

Li Lu commented on YARN-3949:
-----------------------------

bq. The current approach seems to be good now, I propose to go with it, and unblock viewing
the app timeline data after it gets finished. 
+1

bq. Shall we use shutdown and then waitTermination to gracefully stop the service? Otherwise,
if there's a scheduled flush task that is running while the manager invokes writer.close(),
will it cause any problem?

According to Java 7 documentation of shutdownNow:
bq. This method does not wait for actively executing tasks to terminate. Use awaitTermination
to do that.

Seems like we need to protect it by ourselves? 


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

Mime
View raw message