[Gluster-users] GlusterFS 3.8.5 to 3.9 upgrade on CentOS 6.8
momonth at gmail.com
Thu Dec 15 11:49:25 UTC 2016
I noticed that the heal process was not triggered after I upgraded the
3rd (out of 3) node.
Running " # for i in `gluster volume list`; do gluster volume heal $i;
done " didn't trigger any intracluster activity ..
On Tue, Dec 13, 2016 at 5:41 PM, Joe Julian <joe at julianfamily.org> wrote:
> On 12/13/2016 08:00 AM, Momonth wrote:
>>> Are you even using nfs-ganesha?
>>> If not, start by deleting glusterfs-ganesha, then run the update.
>> Not at the moment, however it was deployed and tested previously.
>> I worked it around as follows:
>> # yum remove glusterfs-ganesha-3.8.5-1.el6.x86_64
>> # yum update glusterfs
>> Should I wait till all "heal" processes are finished before proceeding
>> to the next node? I have 2 more nodes running 3.8.5.
> Yes, always wait for heals to finish before shutting down a server (if at
> all possible).
> Gluster-users mailing list
> Gluster-users at gluster.org
More information about the Gluster-users