Fix potential deadlock when connecting to primary master
This is a regression caused by commit eef52c27 ("Tickless poll loop, for lowest latency and cpu usage"), affecting: - admins - storages - primary masters of backup clusters
Showing
Please register or sign in to comment