[jira] [Commented] (KAFKA-584) produce/fetch remote time metric not set correctly when num.acks = 1

["Jun Rao (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484251#comment-13484251 ] 

Jun Rao commented on KAFKA-584:
-------------------------------

Also, volatile makes a long value atomic according to the following article, which is what we want.
http://gee.cs.oswego.edu/dl/cpj/jmm.html
                
> produce/fetch remote time metric not set correctly when num.acks = 1
> --------------------------------------------------------------------
>
>                 Key: KAFKA-584
>                 URL: https://issues.apache.org/jira/browse/KAFKA-584
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.8
>            Reporter: Neha Narkhede
>              Labels: bugs
>             Fix For: 0.8
>
>         Attachments: kafka-584.patch
>
>
> When num.acks = 1, the produce/fetch remote time is set to a very high value (several hours). This is due to a race condition on the apiLocalTime, which is initialized to -1, that makes the (responseTime - apiLocalTime) a very large value.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira