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

Do not pull schema from non-token ring members #611

Merged
merged 2 commits into from
Jan 21, 2021

Conversation

mpenick
Copy link
Contributor

@mpenick mpenick commented Jan 21, 2021

In retrospect, it is a bug to pull schema from non-ring members and schema should only be pulled from the storage nodes. Pulling schema from ring members is handled in theStorageService#onChange() method.

In retrospect, it is a bug to pull schema from non-ring members and schema should only be pulled from the storage nodes. Pulling schema from ring members is handled in the`StorageService#onChange()` method.

// This fix schedules a schema pull for the non-member node and is required because
// `StorageService.onChange()` doesn't do this for non-member nodes.
MigrationManager.instance.scheduleSchemaPull(endpoint, epState);
Copy link
Contributor

Choose a reason for hiding this comment

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

is it feasible to write a test (probably integration test) that checks that the schema from the non-member node is not pulled?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I really don't think so, but I did prove it manually and by analyzing the C*/DSE code.

Copy link
Contributor

@dimas-b dimas-b left a comment

Choose a reason for hiding this comment

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

Only deleted lines :) 👍

@mpenick mpenick merged commit 280d514 into master Jan 21, 2021
@mpenick mpenick deleted the trust-member-schema-only branch January 21, 2021 18:17
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.

None yet

4 participants