You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The tunneldigger clients tries to avoid selecting the same broker again and it again if it gets a connection error. It blacklists a broker upon error and tries the others, until all failed and they all get unblacklisted again.
Unfortunately, I just observed that this can lead to an endless loop: Say two brokers are configured, of which one is offline and one errors. The erroring one will get blacklisted, but the one that is offline will not. Now the client just keeps trying the offline broker, so even if the one that is online stops erroring, it does not get used.
The text was updated successfully, but these errors were encountered:
RalfJung
changed the title
Broker blacklisting can lead to endless loop of some brokers are fully offline
Broker blacklisting can lead to endless loop if some brokers are fully offline
Mar 28, 2019
- fixes broken Broker reset bug in tunneldigger-client wlanslovenija/tunneldigger#87 - now tunneldigger client resets error-tags and starts from scratch, when no Brokers are left over
- added cmake related patches to Makefile
The tunneldigger clients tries to avoid selecting the same broker again and it again if it gets a connection error. It blacklists a broker upon error and tries the others, until all failed and they all get unblacklisted again.
Unfortunately, I just observed that this can lead to an endless loop: Say two brokers are configured, of which one is offline and one errors. The erroring one will get blacklisted, but the one that is offline will not. Now the client just keeps trying the offline broker, so even if the one that is online stops erroring, it does not get used.
The text was updated successfully, but these errors were encountered: