kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-6364) Add Second Check for End Offset During Restore
Date Thu, 01 Feb 2018 23:02:01 GMT

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

ASF GitHub Bot commented on KAFKA-6364:

bbejeck opened a new pull request #4511: KAFKA-6364: second check for ensuring changelog topic
not changed during restore
URL: https://github.com/apache/kafka/pull/4511
   Added a second check for race condition where store changelog topic updated during restore,
but not if a KTable changelog topic. 
   This will be tricky to test, but I wanted to push the PR to get feedback on the approach.
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Add Second Check for End Offset During Restore
> ----------------------------------------------
>                 Key: KAFKA-6364
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6364
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>    Affects Versions: 1.0.0
>            Reporter: Bill Bejeck
>            Assignee: Bill Bejeck
>            Priority: Major
>             Fix For: 1.0.2
> We need to re-check the ending offset when restoring a changelog topic to guard against
the race condition of an additional record appended to log immediately on restoring start.
 Also, need to add a check for KTable source topic and if offset limit is set.

This message was sent by Atlassian JIRA

View raw message