[ https://issues.apache.org/jira/browse/BEAM-6561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17122944#comment-17122944 ]
Beam JIRA Bot commented on BEAM-6561: ------------------------------------- This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3. Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean. > WorkProgressUpdater synchronizes on java.util.concurrent classes > ---------------------------------------------------------------- > > Key: BEAM-6561 > URL: https://issues.apache.org/jira/browse/BEAM-6561 > Project: Beam > Issue Type: Bug > Components: runner-dataflow > Reporter: Kenneth Knowles > Priority: P2 > Labels: stale-P2 > > Findbugs caught this. There seems to be synchronization on variables where > the classes themselves have their own mechanisms. If intended, it should be > made more clear by simple mutexes. -- This message was sent by Atlassian Jira (v8.3.4#803005)