Skip to content

Fix mutation tracking startup #4065

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

Open
wants to merge 1 commit into
base: cep-45-mutation-tracking
Choose a base branch
from

Conversation

bdeggleston
Copy link
Member

No description provided.

@@ -152,7 +152,8 @@ public static void initializeAsNonCmsNode(Function<Processor, Processor> wrapPro
LocalLog.LogSpec logSpec = LocalLog.logSpec()
.withStorage(LogStorage.SystemKeyspace)
.afterReplay(Startup::scrubDataDirectories,
(metadata) -> StorageService.instance.registerMBeans())
(metadata) -> StorageService.instance.registerMBeans(),
MutationTrackingService.instance::start)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MutationTrackingService depends on schema being ready (so we can initialize shards for tracked keyspaces) and internode messaging / native protocol messaging to not be started yet (so we don't receive queries). Any other dependencies for why it has to be started here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason for initializing it via TCM in the first place was because the local node id wasn't always available when we tried to start the tracking service

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