long reconnect times
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 16
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 1
Description
With catalyst multi-node, disconnecting an RTMP stream takes a long time afterward. This happens because incoming connections check against the load balancer, notice that the stream already exists, and exit.
What we should do instead:
* When PUSH_REWRITE fires, we attach a random id to the incoming stream. Stream abc123 gets rewritten to e.g. `video+abc123-ffffff`.
* Catalyst cluster members publish their current streams into the kappa state.
* When nodes want to handle playback, they query that kappa state, discover which stream has the address at which region, and victory.
Contributor guide
No contributing guide indexed for this repository
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 by tracing the PUSH_REWRITE path for incoming RTMP streams and review how Catalyst cluster members publish or query the kappa state. Done means disconnects no longer cause long reconnects, and playback can locate the stream address by region across the cluster.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100