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

Fix local_shotover_broker_id in test configs #1765

Merged
merged 1 commit into from
Oct 4, 2024

Conversation

justinweng-instaclustr
Copy link
Collaborator

@justinweng-instaclustr justinweng-instaclustr commented Oct 3, 2024

Copied from Lucas's comment below:
The local_shotover_broker_id field is currently only used for rack aware routing.
We weren't correctly setting it in our integration tests, the tests still passed since rack aware routing is purely an optimization and not needed for correctness.
We really should fix these configs so that we are running our integration tests with a configuration closer to production.

The way the field works is it configures the broker id that shotover should become.
Shotover looks up the entry in shotover_nodes that has that broker id and acts as that node.

Copy link

codspeed-hq bot commented Oct 3, 2024

CodSpeed Performance Report

Merging #1765 will improve performances by 12.52%

Comparing justinweng-instaclustr:fix-test-configs (d63f072) with main (985668f)

Summary

⚡ 1 improvements
✅ 38 untouched benchmarks

Benchmarks breakdown

Benchmark main justinweng-instaclustr:fix-test-configs Change
encode_system.local_result_v5_no_compression 105.7 µs 94 µs +12.52%

@rukai rukai marked this pull request as ready for review October 3, 2024 23:14
Copy link
Member

@rukai rukai left a comment

Choose a reason for hiding this comment

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

Nice catch!

Context for the next reviewer:
The local_shotover_broker_id field is currently only used for rack aware routing.
We weren't correctly setting it in our integration tests, the tests still passed since rack aware routing is purely an optimization and not needed for correctness.
We really should fix these configs so that we are running our integration tests with a configuration closer to production.

The way the field works is it configures the broker id that shotover should become.
Shotover looks up the entry in shotover_nodes that has that broker id and acts as that node.

@rukai rukai merged commit 0db4f69 into shotover:main Oct 4, 2024
41 checks passed
@justinweng-instaclustr justinweng-instaclustr deleted the fix-test-configs branch October 4, 2024 01:31
rukai pushed a commit to rukai/shotover-proxy that referenced this pull request Oct 8, 2024
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.

3 participants