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
http://voisonics.com/
USA: +1 213 221 1092
New Zealand: +64 (0)28 2558 3782
________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
