[
https://issues.apache.org/jira/browse/KAFKA-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-584:
--------------------------
Attachment: kafka-584.patch
Attach a patch. The problem is that with ack = 1, response could be sent before
apilocaltime is updated. Fixed it by setting apilocatime to responsetime, if
not set. Also, since those times are updated in different threads, make them
volatile so that updates are exposed to other threads. Now, remote times are 0
with ack = 1.
> 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
> 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
