oxidecomputer / oxidecomputer/omicron
Oximeter and blueprint execution could race to initialize a new single-node ClickHouse
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
See comment on #7171.
One solution we discussed is to remove the automatic initialization from the Oximeter client and replace it with a call to the clickhouse-admin /init endpoint in the server. That way, all initialization attempts will be correctly serialized.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the discussion linked from #7171 to understand the race between Oximeter and blueprint execution. Trace the Oximeter client's automatic initialization and the server's clickhouse-admin /init call. Done means initialization attempts for a new single-node ClickHouse are serialized.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100