[Bugs] [Bug 1351071] [geo-rep] Stopped geo-rep session gets started automatically once all the master nodes are upgraded

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1351071

Saravanakumar <sarumuga at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|bugs at gluster.org            |sarumuga at redhat.com



--- Comment #1 from Saravanakumar <sarumuga at redhat.com> ---

Once glusterfs is upgraded (which involves geo-replication slave volume uuid as
part of vol info), if geo-replication status command is run, it creates an
empty monitor.status file (without restarting glusterd daemon)

Now, once the glusterd is restarted after the above step, glusterd updates the
monitor.status file with "Started" state.

This "Started" state gets reflected if you run "gluster volume geo-replication
MasterVolume Slavehost::Slavevolume status" command.

Solution is to avoid updating monitor.status file(with "Started" status) if
monitor.status is empty.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.