Skip to content

Conversation

@dkropachev
Copy link

@dkropachev dkropachev commented Mar 19, 2025

Currently schema agreement logic run select * from system.peers, while only schema_version is used, it creates excessive load on cluster and driver side.

Fixes: #468

@dkropachev dkropachev force-pushed the dk/fix-schema-agreement-query branch from 7df86ce to ea2bf97 Compare March 19, 2025 13:47
@dkropachev dkropachev requested a review from Bouncheck March 19, 2025 13:47
Copy link

@Bouncheck Bouncheck left a comment

Choose a reason for hiding this comment

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

Tests failed due to mocks expecting old call, but this will fail further down the line when checking peer validity which requires at least rpc address.
Just schema_version is not enough, but perhaps some stuff can be limited.

Currently schema agreement logic run `select * from system.peers`, while
only `schema_version` is used, it creates excessive load on cluster and
driver side.
@dkropachev dkropachev force-pushed the dk/fix-schema-agreement-query branch from ea2bf97 to 75214e9 Compare March 19, 2025 14:11
@dkropachev dkropachev closed this Mar 19, 2025
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.

4.x: Don't use overly broad SELECTs when checking schema agreement

2 participants