<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div><br></div><div>Good point Cedric!!<br></div><div>The only thing is that, I would prefer to say "bricks" instead of "nodes" in your statement.<br></div><div><br></div><div>"starting with 4 bricks (3+1) can only evolve by adding 4 bricks (3+1)" <br></div><div><br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Cedric Lemarchand" <yipikai7@gmail.com><br><b>To: </b>"Terry McGuire" <tmcguire@ualberta.ca><br><b>Cc: </b>gluster-users@gluster.org<br><b>Sent: </b>Thursday, March 30, 2017 11:57:27 AM<br><b>Subject: </b>Re: [Gluster-users] Node count constraints with EC?<br><div><br></div><br>> Le 29 mars 2017 à 20:29, Terry McGuire <tmcguire@ualberta.ca> a écrit :<br>> <br>> 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.<br><div><br></div>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. <br><div><br></div>Cheers<br>_______________________________________________<br>Gluster-users mailing list<br>Gluster-users@gluster.org<br>http://lists.gluster.org/mailman/listinfo/gluster-users</div><div><br></div></div></body></html>