Red Hat Bugzilla – Bug 1285211
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-12-02 00:23:17 EST
Expected behavior. In the newly added brick node Geo-rep Monitor process will get restarted, so all the workers in that node also gets restarted.
From documentation, (Chapter 12.5.2)
"When adding a brick to the volume on an existing node in the trusted storage pool with a geo-replication session running, the geo-replication daemon on that particular node will automatically be restarted. The new brick will then be recognized by the geo-replication daemon. This is an automated process and no configuration changes are required. "
Closing this bug, Please reopen if found again.