This is a tracking issue for all the work related to deploying multi-node clickhouse on a running system via reconfigurator. We expect that each system will run both single and multi-node for a while per RFD 468 and reconfigurator should allow us to transition between the two at runtime. We likely will need to change RSS to also deploy single and multi-node clickhouse to support this.
Reconfigurator:
[x] #6298
[x] #6299
[x] Add CRDB blueprint tables related to clickhouse configuration
[x] Add planner code for deploying single node and multi-node clickhouse
[x] Add logic and tests to generate a configuration - ClickhouseAllocator
[x] Integrate ClickhouseAllocator into blueprint and db queries
[x] Add planner code for enabling multi-node clickhouse
[x] Add clickhouse configuration to RSS service plan (or punt to reconfigurator)
[x] Add executor code to deploy single and multi-node clickhouse
[x] Add executor code to enable multi-node clickhouse
[x] Add omdb support for reconfigurator deployment of clickhouse
[ ] Add omdb support for inspection/debugging of clickhouse
karencfv
commented
2 months ago
This is a tracking issue for all the work related to deploying multi-node clickhouse on a running system via reconfigurator. We expect that each system will run both single and multi-node for a while per RFD 468 and reconfigurator should allow us to transition between the two at runtime. We likely will need to change RSS to also deploy single and multi-node clickhouse to support this.
Reconfigurator:
ClickhouseAllocatorClickhouseAllocatorinto blueprint and db queriesSled-agent:
clickhouse_serverzone and move all replicated clickhouse related code there https://github.com/oxidecomputer/omicron/pull/6343