[
https://issues.apache.org/jira/browse/KAFKA-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402802#comment-13402802
]
Jay Kreps commented on KAFKA-353:
---------------------------------
The guard is checked before the call to expire. The invariant here is everyone
must do a test-and-set on the satisfied variable and only proceed with handling
the request if it is satisfied. I don't think there is any problem with
checkSatisfied being called on an item that is going to be expired it is only a
problem if we try to process the request twice (the call to check satisfied or
expire will end up being redundant work but that is not a major problem).
> tie producer-side ack with high watermark and progress of replicas
> ------------------------------------------------------------------
>
> Key: KAFKA-353
> URL: https://issues.apache.org/jira/browse/KAFKA-353
> Project: Kafka
> Issue Type: Sub-task
> Affects Versions: 0.8
> Reporter: Jun Rao
> Assignee: Joel Koshy
> Attachments: kafka-353_v1.patch, kafka-353_v2.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
