Opened 2 years ago
Pull relays do not reconnect, recover on 2.0.36
|Reported by:||Owned by:||stoecker|
We have run into an issue with relays reconnecting to sources that go away and then come back. Our relevant configuration is:
relay pull -i u:p -m /RTCM3EPH products.igs-ip.net:2101/RTCM3EPH
I'm going through the code trying to understand how timeouts to read connections like this would be applied. Is there some configuration we're missing that could help us recover quickly?
We had a recent outage where our BKG relay did not recover after a relay source went down for 15 minutes - the BKG relay stayed down for 2 hours, while our other caster (a SNIP) recovered the stream after 15 minutes.
Any advice in debugging this would be very appreciated. I'm thinking about adding a setsockopt call with SOL_TCP and TCP_USER_TIMEOUT on the sockets to improve timeouts.