This message was deleted.
# harvester
a
This message was deleted.
b
The only item we can see in the events page for the volume is Removing unknown replica tcp://10.138.31.19:10694 in mode ERR from engine The volume will happily operate with an additional replica indefinitely until we decrease the replica count so don't think the new replica itself is the issue
Ah looks like replica auto balance, which I thought only applied when new nodes where added but I guess gets triggered on replica count updates as well