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

Initializing the shard positions actor with the existing cluster state #4621

Merged
merged 2 commits into from
Feb 26, 2024

Conversation

fulmicoton
Copy link
Contributor

on startup.

Chitchat is started before everything else, so we might be missing some positions if we just start listening for updates.

@fulmicoton fulmicoton force-pushed the initialize-shard-positions branch 2 times, most recently from 84234d7 to 496ec2f Compare February 22, 2024 08:45
quickwit/quickwit-indexing/src/models/shard_positions.rs Outdated Show resolved Hide resolved
quickwit/quickwit-serve/src/lib.rs Outdated Show resolved Hide resolved
fulmicoton and others added 2 commits February 26, 2024 10:45
We had two problems here.
a) the ingester loads in an asynchronous fashion, as it needs to replay
the WAL entirely.
Subscribing to shard positions events is part of this initialization.
We could be missing all of the event received before the initialization (via chitchat).
b) we start the cluster first. Long after we in the initialization
process, we start the ShardPositionsService. We could possibly be
missing the keys that were shared in between.

Closes #4622
Co-authored-by: Adrien "Code Monkey" Guillo <[email protected]>
@fulmicoton fulmicoton enabled auto-merge (squash) February 26, 2024 01:46
@fulmicoton fulmicoton merged commit 8e1f0be into main Feb 26, 2024
4 checks passed
@fulmicoton fulmicoton deleted the initialize-shard-positions branch February 26, 2024 02:02
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 this pull request may close these issues.

2 participants