You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Marcelo Vanzin (JIRA)" <ji...@apache.org> on 2016/03/04 21:47:40 UTC

[jira] [Commented] (SPARK-13684) Possible unsafe bytesRead increment in StreamInterceptor

    [ 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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org