hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6455) Enhance the timelinewriter.flush() race condition fix
Date Thu, 27 Apr 2017 12:57:04 GMT

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

Hudson commented on YARN-6455:

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11639 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/11639/])
YARN-6455. Enhance the timelinewriter.flush() race condition fix (Haibo (varunsaxena: rev
* (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice/src/main/java/org/apache/hadoop/yarn/server/timelineservice/collector/TimelineCollector.java
* (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice/src/main/java/org/apache/hadoop/yarn/server/timelineservice/collector/AppLevelTimelineCollector.java

> Enhance the timelinewriter.flush() race condition fix
> -----------------------------------------------------
>                 Key: YARN-6455
>                 URL: https://issues.apache.org/jira/browse/YARN-6455
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: yarn
>    Affects Versions: 3.0.0-alpha2
>            Reporter: Haibo Chen
>            Assignee: Haibo Chen
>             Fix For: YARN-5355, YARN-5355-branch-2, 3.0.0-alpha3
>         Attachments: YARN-6455.00.patch
> YARN-6376 fixes timelinewriter.flush() race condition among concurrent putEntities()
calls and periodical flush by TimelineCollectorManager by synchronizing on the writer object.

> Synchronizing on the writer is still a little brittle there, because there is a getWriter
method which lets callers access the writer without synchronizing on it. AppLevelTimelineCollector#AppLevelAggregator#agregate()
does this in line 152: getWriter().write(...)  In this case it doesn't flush, but if that
were to be added, that would re-introduce the race fixed in YARN-6376.
> Instead of exposing the writer, perhaps it would be better to have the sub-classes call
#putEntities instead. It defers to the private writeTimelineEntities which does the same work
to get the context:
> TimelineCollectorContext context = getTimelineEntityContext();

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message