oxidecomputer / oxidecomputer/omicron
database flakiness on a4x2
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
I haven't dug much into this but I have noticed doing Reconfigurator work on a4x2 that we get a decent number of what look like transient CockroachDB errors like the ones mentioned in #8860. Here are some example messages:
InternalError { internal_message: "unexpected database error: inbox communication error: rpc error: code = Canceled desc = context canceled" }
InternalError { internal_message: "unexpected database error: no inbound stream connection" }
and general client-side "operation timed out".
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
The issue names no files or tests; start by comparing the reported CockroachDB messages with issue #8860 and reproducing them during Reconfigurator work on a4x2. Investigate the canceled inbox communication, missing inbound stream, and client-side timeout cases; done should identify the cause and establish that the affected workload no longer exhibits the flakiness.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100