hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vrushali C (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-3650) Consider concurrency situations for TimelineWriter
Date Sat, 19 Aug 2017 05:34:02 GMT

     [ https://issues.apache.org/jira/browse/YARN-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Vrushali C updated YARN-3650:
    Parent Issue: YARN-7055  (was: YARN-5355)

> Consider concurrency situations for TimelineWriter
> --------------------------------------------------
>                 Key: YARN-3650
>                 URL: https://issues.apache.org/jira/browse/YARN-3650
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Vrushali C
>              Labels: YARN-5355
> [~jrottinghuis] brought up an interesting point in YARN-3411. Filing jira to track to
discuss and handle the following: 
> For TimelineWriter and its implementations, is there an expectation set around
> concurrency? Is any synchronization expected / needed to ensure visibility when calls
happen from different threads?
> How about entities, are they expected to be immutable once passed to the write method?
> Similarly for the constructor, we're assuming that the configuration object will not
be modified while we're constructing a TimelineWriter?

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