You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean R. Owen (Jira)" <ji...@apache.org> on 2020/01/03 17:43:00 UTC
[jira] [Assigned] (SPARK-30406) OneForOneStreamManager use
AtomicLong
[ https://issues.apache.org/jira/browse/SPARK-30406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean R. Owen reassigned SPARK-30406:
------------------------------------
Assignee: Ajith S
> 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
>
> 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: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org