[
https://issues.apache.org/jira/browse/SPARK-30406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean R. Owen resolved SPARK-30406.
----------------------------------
Fix Version/s: 3.0.0
Resolution: Fixed
Issue resolved by pull request 27071
[https://github.com/apache/spark/pull/27071]
> OneForOneStreamManager use AtomicLong
> -------------------------------------
>
> Key: SPARK-30406
> URL: https://issues.apache.org/jira/browse/SPARK-30406
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 3.0.0
> Reporter: Ajith S
> Assignee: Ajith S
> Priority: Minor
> Fix For: 3.0.0
>
>
> Using compound operations as well as increments and decrements on primitive
> fields are not atomic operations. Here when volatile primitive field is
> incremented or decremented, we run into data loss if threads interleave in
> steps of update.
>
> Refer:
> [https://wiki.sei.cmu.edu/confluence/display/java/VNA02-J.+Ensure+that+compound+operations+on+shared+variables+are+atomic]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
