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

source split change may use stale cache #15591

Open
xxchan opened this issue Mar 11, 2024 · 1 comment
Open

source split change may use stale cache #15591

xxchan opened this issue Mar 11, 2024 · 1 comment
Assignees
Labels
component/connector type/bug Something isn't working
Milestone

Comments

@xxchan
Copy link
Member

xxchan commented Mar 11, 2024

          > For existing splits, we should use the latest offset from the cache. `target_splits` is from meta and contains the initial offset.

I'm unsure whether this is always correct when scaling. The ideas are similar to the documentation on the function cache_may_stale. The safest way should be always recovering states from the state store.

Originally posted by @BugenZhao in #14172 (comment)

Copy link
Contributor

This issue has been open for 60 days with no activity. Could you please update the status? Feel free to continue discussion or close as not planned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/connector type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants