livepeer / livepeer/go-livepeer
dms-api: Add stream cleanup after timeout
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 586
- Forks
- 226
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 19
Description
We should introduce a mechanism for cleaning up streams from:
- Stream Cache
- Mist
Otherwise, in case any issues with the stream Upload/Transcoding, we may end up with a number of streams created in Mist and in our Stream Cache.
I think we should agree on some timeout for the stream processing and after the timeout is reached, we clean up Mist and Stream Cache, the same way it's already done after receiving the Push End trigger.
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 Push End cleanup logic in handlers/handlers.go, then trace the stream upload and transcoding flow that creates entries in Mist and Stream Cache. Define the processing timeout and ensure both resources are cleaned up after it, matching the existing Push End behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100