livepeer / livepeer/go-livepeer
add ability to trigger transcoder health-check from the CLI port
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 586
- Forks
- 226
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 19
Description
Orchestrators already the ability to self-check that they can transcode, and they do so on boot. We run into problems with "stuck Os" from time to time. If we add the ability to trigger the transcode self-check from the CLI port (perhaps POST http://localhost:7935/self-check), we can easily build a Kubernetes livenessProbe that will terminate stuck Os if they can no longer transcode.
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
Locate the CLI port handler and the existing orchestrator transcode self-check that runs on boot. Determine how a POST to /self-check should invoke that check and report success or failure, then add coverage for the endpoint and verify the result is usable as a Kubernetes livenessProbe.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100