Red Hat Bugzilla – Bug 820428
[RFE] Geo-replication is not automatically restarted on remaining Masters
Last modified: 2015-04-09 07:05:58 EDT
Description of problem:
Starting geo-replication on a replicated volume only ever starts the gsyncd processes on the node where the command was executed. There is no automatic restard of geo-replication in case that node dies.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start geo-replication on node1
2. reset node1
3. check geo-replication status on remaining node
Geo-replication is not running
Geo-replication is running
Feature requests make most sense against the 'mainline' release, there is no ETA for an implementation and requests might get forgotten when filed against a particular version.
This is not applicable with the Distributed Geo-replication from >3.5. Closing this bug. Please reopen if issue found again.