Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Partitioned sources revoke/assign ignore re-assigned partitions #570

Closed
ennru opened this issue Sep 25, 2018 · 6 comments · Fixed by #590
Closed

Partitioned sources revoke/assign ignore re-assigned partitions #570

ennru opened this issue Sep 25, 2018 · 6 comments · Fixed by #590
Milestone

Comments

@ennru
Copy link
Member

ennru commented Sep 25, 2018

#382 reported lost messages on partition reassignment. This was solved (or at least improved) with #462 and #517, by delaying the actual handling of the revoked topic partitions: SubSourceLogic.partitionRevokedCB

This does not work correctly whenever the Kafka client issues revoke and assign signals for the same partitions within the timeframe of waitClosePartition. Whenever that happens any assigned partitions - that were marked as revoked just before - will be ignored: SubSourceLogic.partitionAssignedCB.

@ennru
Copy link
Member Author

ennru commented Sep 28, 2018

This issue becomes visible when using manual offsets via plainPartitionedManualOffsetSource.

@tkroman
Copy link

tkroman commented Oct 4, 2018

See also #539. AFAIU #590 only works for external storage, right? I’m still willing to put some work into my original issue if I had some pointers on how to approach this, please let me know if there is anything I can do.

@2m 2m closed this as completed in #590 Oct 4, 2018
@2m 2m added this to the 1.0-M1 milestone Oct 4, 2018
@ennru
Copy link
Member Author

ennru commented Oct 5, 2018

@tkroman Thanks for pointing this out. Yes, #590 just changed what partitions are passed to the function fetching offsets from external storage.

@Camsteack
Copy link

@ennru Thanks a lot for the quick fix

@2m
Copy link
Contributor

2m commented Oct 5, 2018

If you would like to try out a snapshot version with this fix merged in, we have just released a 0.22+75-ada5b3a2 to the snapshots repo.

@Camsteack
Copy link

Will do !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants