Update upgrade guide with instructions for glustereventsd #410
Conversation
Upgrade guide did not specify stopping and restarting glustereventsd and these instructions are now added to the 3.12 and 4.1 upgrade guides, as these are the current supported releases. Signed-off-by: ShyamsundarR <srangana@redhat.com>
Signed-off-by: ShyamsundarR <srangana@redhat.com>
| @@ -42,18 +43,23 @@ This procedure involves upgrading **one server at a time**, while keeping the vo | |||
| #gluster volume status | |||
| ``` | |||
|
|
|||
| 7. Self-heal all gluster volumes by running | |||
| 7. Start glustereventsd service (if it was enabled before), either using the command below, or through other means, | |||
There was a problem hiding this comment.
If the glustereventsd service was previously enabled, it is required to start it using the commands below, or, through other means
| #systemctl start glustereventsd | ||
| ``` | ||
|
|
||
| 8. Self-heal all gluster volumes by running |
There was a problem hiding this comment.
Invoke self-heal on all the gluster volumes by running
| ```sh | ||
| #for i in `gluster volume list`; do gluster volume heal $i; done | ||
| ``` | ||
|
|
||
| 8. Ensure that there is no heal backlog by running the below command for all volumes | ||
| 9. Ensure that there is no heal backlog by running the below command for all volumes |
There was a problem hiding this comment.
Verify that there are no heal backlog by running the command for all the volumes
| ```sh | ||
| #gluster volume heal <volname> info | ||
| ``` | ||
| > NOTE: If there is a heal backlog, wait till the backlog is empty, or the backlog does not have any entries needing a sync to the just upgraded server, before proceeding to upgrade the next server in the pool | ||
| > **NOTE:** If there is a heal backlog, wait till the backlog is empty, or the backlog does not have any entries needing a sync to the just upgraded server, before proceeding to upgrade the next server in the pool |
There was a problem hiding this comment.
Before proceeding to upgrade the next server in the pool it is recommended to check the heal backlog. If there is a heal backlog, it is recommended to wait until the backlog is empty, or, the backlog does not contain any entries requiring a sync to the just upgraded server.
| @@ -84,7 +91,12 @@ This procedure involves cluster downtime and during the upgrade window, clients | |||
| #gluster volume status | |||
| ``` | |||
|
|
|||
| 7. Restart any gfapi based application stopped previously in step (2) | |||
| 7. Start glustereventsd service (if it was enabled before), either using the command below, or through other means, | |||
There was a problem hiding this comment.
If the glustereventsd service was previously enabled, it is required to start it using the commands below, or, through other means
docs/Upgrade-Guide/upgrade_to_4.1.md
Outdated
| @@ -84,7 +91,12 @@ This procedure involves cluster downtime and during the upgrade window, clients | |||
| #gluster volume status | |||
| ``` | |||
|
|
|||
| 7. Restart any gfapi based application stopped previously in step (2) | |||
| 7. Start glustereventsd service (if it was enabled before), either using the command below, or through other means, | |||
There was a problem hiding this comment.
If the glustereventsd service was previously enabled, it is required to start it using the commands below, or, through other means
docs/Upgrade-Guide/upgrade_to_4.1.md
Outdated
| ```sh | ||
| #gluster volume heal <volname> info | ||
| ``` | ||
| > NOTE: If there is a heal backlog, wait till the backlog is empty, or the backlog does not have any entries needing a sync to the just upgraded server, before proceeding to upgrade the next server in the pool | ||
| > **NOTE:** If there is a heal backlog, wait till the backlog is empty, or the backlog does not have any entries needing a sync to the just upgraded server, before proceeding to upgrade the next server in the pool |
There was a problem hiding this comment.
Before proceeding to upgrade the next server in the pool it is recommended to check the heal backlog. If there is a heal backlog, it is recommended to wait until the backlog is empty, or, the backlog does not contain any entries requiring a sync to the just upgraded server.
docs/Upgrade-Guide/upgrade_to_4.1.md
Outdated
| ```sh | ||
| #for i in `gluster volume list`; do gluster volume heal $i; done | ||
| ``` | ||
|
|
||
| 8. Ensure that there is no heal backlog by running the below command for all volumes | ||
| 9. Ensure that there is no heal backlog by running the below command for all volumes |
There was a problem hiding this comment.
Verify that there are no heal backlog by running the command for all the volumes
docs/Upgrade-Guide/upgrade_to_4.1.md
Outdated
| #systemctl start glustereventsd | ||
| ``` | ||
|
|
||
| 8. Self-heal all gluster volumes by running |
There was a problem hiding this comment.
Invoke self-heal on all the gluster volumes by running
Addresses review comments in the previous commit. Signed-off-by: ShyamsundarR <srangana@redhat.com>
|
I have verified that @sankarshanmukhopadhyay's comments have been addressed. |
Upgrade guide did not specify stopping and restarting glustereventsd
and these instructions are now added to the 3.12 and 4.1 upgrade
guides, as these are the current supported releases.
Signed-off-by: ShyamsundarR srangana@redhat.com