Skip to content

[clickhouse] replicated and single-node config should match#10454

Merged
karencfv merged 2 commits into
oxidecomputer:mainfrom
karencfv:keep-replica-config-in-sync
May 18, 2026
Merged

[clickhouse] replicated and single-node config should match#10454
karencfv merged 2 commits into
oxidecomputer:mainfrom
karencfv:keep-replica-config-in-sync

Conversation

@karencfv
Copy link
Copy Markdown
Contributor

@karencfv karencfv commented May 18, 2026

Follow up to #10443 and #10450 . We should keep both configs in sync

@karencfv karencfv requested review from bnaecker and jmcarp May 18, 2026 06:14
Copy link
Copy Markdown
Contributor

@jmcarp jmcarp left a comment

Choose a reason for hiding this comment

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

Thanks for reconciling! For another time, I wonder if we should consolidate single and clustered config generation in clickhouse-admin—but maybe it's not worth doing if single-node is going away?

@karencfv
Copy link
Copy Markdown
Contributor Author

I wonder if we should consolidate single and clustered config generation in clickhouse-admin—but maybe it's not worth doing if single-node is going away?

We've been saying it's going to go away for a couple of years now, and it hasn't yet 😄 If it's not more than an hour's worth of work, perhaps it's worth it if only to keep both configs in sync?

@karencfv karencfv merged commit 5af8047 into oxidecomputer:main May 18, 2026
16 checks passed
@karencfv karencfv deleted the keep-replica-config-in-sync branch May 18, 2026 21:31
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