Thanks Ashish, Cedric, for your comments. I’m no longer concerned about my choice of 4 nodes to start, but, I realize that there’s an issue with my subvolume config options. Turns out only my 8+3 choice is permitted, as the 4+2 and 8+4 options violate the data/parity>2 rule. So, 8+3 it is, as 8+2 isn’t quite enough redundancy for me.
Regards, Terry > On Mar 30, 2017, at 02:14, [email protected] wrote: > > On 30/03/2017 08:35, Ashish Pandey wrote: >> 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)" > Oh right, thanks for correcting me ! > > Cheers > >> >> From: "Cedric Lemarchand" <[email protected]> <mailto:[email protected]> >> To: "Terry McGuire" <[email protected]> <mailto:[email protected]> >> Cc: [email protected] <mailto:[email protected]> >> Sent: Thursday, March 30, 2017 11:57:27 AM >> Subject: Re: [Gluster-users] Node count constraints with EC? >> >> >> > Le 29 mars 2017 à 20:29, Terry McGuire <[email protected]> >> > <mailto:[email protected]> 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 >> [email protected] <mailto:[email protected]> >> http://lists.gluster.org/mailman/listinfo/gluster-users >> <http://lists.gluster.org/mailman/listinfo/gluster-users> >> >
_______________________________________________ Gluster-users mailing list [email protected] http://lists.gluster.org/mailman/listinfo/gluster-users
