Problem solved, more or less.
After reading Aytac's comment about 3.6.2 not being considered
stable yet I removed it from the new node, removed
/var/lib/glusterd/, rebooted (just to be sure) and installed 3.5.3.
After detaching and re-probing the peer the replace-brick command
worked and the volume is currently happily undergoing a self-heal.
At a later and more convenient time I'll upgrade the 3.4.2 node to
the same version. As previously stated, I cannot upgrade the
clients, so they will just have to stay where they are.
regards,
John
On 25/02/15 08:27, aytac zeren wrote:
Hi John,
3.6.2 is a major release and introduces some new features in
cluster wide concept. Additionally it is not stable yet. The
best way of doing it would be establishing another 3.6.2
cluster, accessing 3.4.0 cluster via nfs or native client, and
copying content to 3.6.2 cluster gradually. While your volume
size decreases on 3.4.0 cluster, you can unmount 3.4.0 members
from cluster, upgrade them and add 3.6.2 trusted pool with
brick. Please be careful while doing this operation, as number
of nodes in your cluster should be reliable with your cluster
design. (Stripped, Replicated, Distributed or a combination of
them).
Notice: I don't take any responsibility on the actions you
have undertaken with regards to my recommendations, as my
recommendations are general and does not take your
archtiectural design into consideration.
BR
Aytac
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud
service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
|
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
