Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Relay Push mode #27

Open
VideoFX opened this issue Jul 20, 2022 · 6 comments
Open

Relay Push mode #27

VideoFX opened this issue Jul 20, 2022 · 6 comments
Labels
enhancement New feature or request

Comments

@VideoFX
Copy link

VideoFX commented Jul 20, 2022

This is amazing, i am trying it today for the first time. I came here looking for a relay push mode to experiment with. I am wondering if there is a way to achieve this with srtrelay. Is there a feature, similar to sls, where you can specify a relay type push method to push it to another srtrelay node?

This is fantastic btw, thank you. Testing now.

@ravenium
Copy link
Contributor

I cobbled together something to do that - apologies as it might be a little dusty but should still work: https://github.com/ravenium/fragconsole . Basically you'd run it with -f and specify a relay. Our use case was getting users with spotty ISPs onto a local reflector, then having that reflector utilize our internal backbone for transport. Is that sort of what you're looking to do?

@VideoFX
Copy link
Author

VideoFX commented Jul 21, 2022

Yes exactly what I am doing! Thank you @ravenium I will check it.

@iSchluff
Copy link
Member

I was thinking about implementing automatic reflection using consul as synchronization backend. Basically similar to sls clustering for rtmp. Pulling a stream from one of the relays would automatically fetch it from the origin.

@ravenium
Copy link
Contributor

@iSchluff I like the idea, but maybe redis as a backend would keep it simpler for the average docker-compose user?

I've been looking for an excuse to k8s-ify this but I couldn't find a good way to find out which backend is ingesting what stream.

@iSchluff iSchluff added the enhancement New feature or request label Oct 31, 2022
@iSchluff
Copy link
Member

@ravenium well redis is not easily distributed, so there would be no benefit to using it. There would be ways to do this without an additional piece software, it's just more complicated. e.g. using https://github.com/hashicorp/memberlist and distributing data between manually

@ravenium
Copy link
Contributor

You're probably onto a better solution - I was thinking of just pointing all of them at a central redis container as a sort of state tracking, but then again that probably wouldn't account for dead/stale nodes and...well, a lot of things :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants