I have two liverepeater-edge applications talking to two liverepeater-origin applications (which are doing the HLS packetizing).
The Repeater configuration is as follows:
For simplicity, I'll refer to these servers 133 and 165. :-)
If I have a working stream pushing to 133's liverepeater-origin, a request to 133's liverepeater-edge immediately returns a 200.
If there is a working stream pushing to 165 but *not* to 133, then a request to 133's liverepeater-edge takes a while to return a 404, then I can see in its logs that it's failing over to using 165 as the origin, after which subsequent requests to 133's liverepeater-edge immediately return a 200.
It boils down to this: The liverepeater-edge has to discover that its OriginURL is failing before trying the other, and it only does so AFTER the first request.
Is there a way to work around this, or is it something I should raise as a bug?