Nikolay Seliverstov

Today is also no leaks. I think this is kind of config propagation error or faulty state of replicas which back to normal after their leak-oom-restart loop. We didn't restart...

Today a leak happened on replica that last time leaked before the config change and no restarts since then. My current observation is that after the config change there were...

 The green is the leaking master. After that some replicas stopped to synchronize with "Partial resynchronization not possible (no cached master)" We had to stop and start the whole...

I have some information about new case we had today at around 07:48/10:48 (logs with different timezones). These are the logs from leaked master: ``` 1248150:M 25 Dec 2023 07:43:20.760...

I have degoogled phone but I'll see what I can do.