[
https://issues.apache.org/jira/browse/SPARK-13684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180515#comment-15180515
]
Marcelo Vanzin commented on SPARK-13684:
----------------------------------------
It's not a real bug; netty guarantees that, on the read pipeline, a single
thread is running the handlers. The volatile is there for paranoia, in case two
back-to-back handler invocations happen on different threads.
> 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
