[ https://issues.apache.org/jira/browse/KAFKA-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dong Lin resolved KAFKA-6285. ----------------------------- Resolution: Duplicate Duplicate of KAFKA-6285 > OffsetCommitRequest should have read-after-write logic > ------------------------------------------------------ > > Key: KAFKA-6285 > URL: https://issues.apache.org/jira/browse/KAFKA-6285 > Project: Kafka > Issue Type: Bug > Reporter: Dong Lin > Assignee: Dong Lin > > Currently OffsetCommitRequest does not have read-after-write logic and a > consumer can possibly read an older offset value after successfully > committing the offset. This is because broker may respond to > OffsetCommitRequest before writing offset to the disk and the memory. > This is probably not a problem for most users who do not immediately read > offset after committing offset. But it can be a problem if broker fails > before writing offset to disk. It will be nice if we can have > read-after-write logic for OffsetCommitRequest. -- This message was sent by Atlassian JIRA (v6.4.14#64029)