[
https://issues.apache.org/jira/browse/YARN-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohith Sharma K S resolved YARN-3650.
-------------------------------------
Resolution: Won't Fix
In ATSv2 weekly call, discussed for cleaning up JIRA which are not going
implement. Hence, closing the JIRA as Won't Fix. Feel free to reopen if still
same design approach exists.
> 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
> Priority: Major
> 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
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
