Good point Cedric!!
The only thing is that, I would prefer to say "bricks" instead of "nodes" in your statement.
"starting with 4 bricks (3+1) can only evolve by adding 4 bricks (3+1)"
From: "Cedric Lemarchand" <yipikai7@xxxxxxxxx>
To: "Terry McGuire" <tmcguire@xxxxxxxxxxx>
Cc: gluster-users@xxxxxxxxxxx
Sent: Thursday, March 30, 2017 11:57:27 AM
Subject: Re: Node count constraints with EC?
> Le 29 mars 2017 à 20:29, Terry McGuire <tmcguire@xxxxxxxxxxx> a écrit :
>
> I was thinking I’d spread these over 4 nodes, and add single nodes over time, with subvolumes rearranged over new nodes to maintain protection from whole node failures.
Also keep in mind that dispersed cluster can only be expanded by the number of initial nodes, eg starting with 4 nodes 3+1 can only evolve by adding 4 nodes 3+1, you cannot change the default policy 3+1 to 4+1. So the granularity of the evolution of the cluster is fixed at the beginning.
Cheers
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users
To: "Terry McGuire" <tmcguire@xxxxxxxxxxx>
Cc: gluster-users@xxxxxxxxxxx
Sent: Thursday, March 30, 2017 11:57:27 AM
Subject: Re: Node count constraints with EC?
> Le 29 mars 2017 à 20:29, Terry McGuire <tmcguire@xxxxxxxxxxx> a écrit :
>
> I was thinking I’d spread these over 4 nodes, and add single nodes over time, with subvolumes rearranged over new nodes to maintain protection from whole node failures.
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
