[jira] [Updated] (YARN-3650) Consider concurrency situations for TimelineWriter
[ 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 (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-3650) Consider concurrency situations for TimelineWriter
[ https://issues.apache.org/jira/browse/YARN-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joep Rottinghuis updated YARN-3650: --- Parent Issue: YARN-5355 (was: YARN-2928) > 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 (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-3650) Consider concurrency situations for TimelineWriter
[ https://issues.apache.org/jira/browse/YARN-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joep Rottinghuis updated YARN-3650: --- Labels: YARN-5355 (was: ) > 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 (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
