nip
nip
Hi, @jan--f It's a bit complicated - during finding this, I run 3 nodes of Alertmanager, one of them in debugger It's appears only on cluster mode with big notification...
> a dupplicate gossip message for oversized messages Currently, there's no sync between nodes with big messages (reason of duplication on receiver) and flood by broadcasting `n` times other logs...
In my solution, all logs will be announced further once
Hi @Spaceman1701 , Yep, it caused by source code as mentioned in fix #4153 It doesn't depend from configuration files and content of alerts, only on size of notification log...
It was consistent before my fix, yep In case of big amount of incoming alerts from several identical vmalert ('cause of fault-tolerance) to each of Alertmanager nodes led to case...