Red Hat Bugzilla – Bug 1031970
Dist-geo-rep : after brick was added to a volume from existing node, all the gsyncd processes in that node will be restarted.
Last modified: 2015-11-25 03:51:01 EST
Description of problem: after brick was added to a volume from existing node, all the gsyncd processes in that node will be restarted.
Version-Release number of selected component (if applicable):glusterfs-18.104.22.168rhs-1
How reproducible: happens every time
Steps to Reproduce:
1.create and start a geo-rep relationship between master and slave.
2.add brick to the master volume in the existing nodes.
Actual results: all the existing gsyncds on those nodes will be restarted.
Expected results: It shouldn't restart existing gsyncds.
Closing this bug since RHGS 2.1 release reached EOL. Required bugs are cloned to RHGS 3.1. Please re-open this issue if found again.