[
https://issues.apache.org/jira/browse/SPARK-13684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180575#comment-15180575
]
holdenk commented on SPARK-13684:
---------------------------------
It should (coverity doesn't trigger on any of the places where we use
AtomicLong), although getting rid of the volatile keyword should also remove
the warning (looking at the netty docs
http://netty.io/wiki/new-and-noteworthy-in-4.0.html#wiki-h2-34 "A user does not
need to define a volatile field to keep the state of a handler.")
> Possible unsafe bytesRead increment in StreamInterceptor
> --------------------------------------------------------
>
> Key: SPARK-13684
> URL: https://issues.apache.org/jira/browse/SPARK-13684
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Reporter: holdenk
> Priority: Trivial
>
> We unsafely increment a volatile (bytesRead) in a call back, if two call
> backs are triggered we may under count bytesRead. This issue was found using
> coverity.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
