Hi Aytac,
Thanks for the reply but none of it answers my question.
Nevertheless, what's wrong with simply upgrading the nodes? Your
suggested method sounds extremely dangerous and not something I
would ever contemplate for a production system, even if we did have
that kind of storage space and nodes just lying around unused (we
definitely do not). I also don't understand what you mean by "While
your volume size decreases on 3.4.0 cluster, you can unmount 3.4.0
members from cluster". Making a copy doesn't alter the size of the
original.
Please also note that I have already stated that we are locked in
with the client version and cannot upgrade them. That's controlled
by Red Hat, not us.
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
