Gluster users - Aug 2020 - Geo-replication force active server

Hello,

We have geo-replication, and one of the nodes on the primary side (in
mirror replication with the other primary nodes), is acting a little badly.
These have been mentioned in other emails to the list about high CPU usage
and not closing log files.

At the moment it's hard to tell whether the problems are because this is
the active geo-replication push node, or if it's something else to do with
the server it's running on.

How can we force a particular node to be the active geo-replication push
node?

If we can make a different node the push and the problems move too, then we
know it's geo-replication and not the server that's the problem.

Thanks in advance,

-- 
David Cunningham, Voisonics Limited
http://voisonics.com/
USA: +1 213 221 1092
New Zealand: +64 (0)28 2558 3782
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20200827/7d7964b8/attachment.html>