• Julien Muchembled's avatar
    Do not reconnect too quickly to a node after an error · d898a83d
    Julien Muchembled authored
    For example, a backup storage node that was rejected because the upstream
    cluster was not ready could reconnect in loop without delay, using 100% CPU
    and flooding logs.
    
    A new 'setReconnectionNoDelay' method on Connection can be used for cases where
    it's legitimate to quickly reconnect.
    
    With this new delayed reconnection, it's possible to remove the remaining
    time.sleep().
    d898a83d
Name
Last commit
Last update
neo Loading commit data...
tools Loading commit data...
.gitignore Loading commit data...
BUGS Loading commit data...
CHANGES Loading commit data...
COPYING Loading commit data...
MANIFEST.in Loading commit data...
README Loading commit data...
TESTS.txt Loading commit data...
TODO Loading commit data...
UPGRADE Loading commit data...
ZODB3.patch Loading commit data...
importer.conf Loading commit data...
neo.conf Loading commit data...
neoadmin Loading commit data...
neoctl Loading commit data...
neolog Loading commit data...
neomaster Loading commit data...
neomigrate Loading commit data...
neostorage Loading commit data...
setup.py Loading commit data...