oxidecomputer / oxidecomputer/omicron

nexus `external_endpoints` task hung

Open
#9,715 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
572
Forks
97
Avg merge
2d 12h
Merged PRs (30d)
96

Description

This was observed in our colo environment and (internal) details are under oxidecomputer/colo#148.

The upshot is that some runaway automation created a ton of TLS certificates again and in one of the three Nexus instances, the external_endpoints task got hung, apparently for days. The root cause is still being determined but appears to be a missed wakeup in the kernel on the database side. This ticket will cover the analysis and information about mitigation and workarounds. More details coming!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Nexus external_endpoints task and the investigation referenced in oxidecomputer/colo#148. The issue says the work is still analysis; done means identifying the cause of the hang and documenting effective mitigation and workarounds.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.