[
https://issues.apache.org/jira/browse/SPARK-13684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181647#comment-15181647
]
Sean Owen commented on SPARK-13684:
-----------------------------------
Hm OK this turns out to be a non-issue. I guess I think it's worth removing
volatile then. Like the scanner, I'd also read this assuming it was there for
correctness when multiple threads access and then maybe be surprised it's not
used that way. @holdenk I'd say it's your call what to do.
> 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
