----- Original Message ----- > > For the short-term, wouldn't it be OK to disallow adding bricks that > > is not a multiple of group-size? > > In the *very* short term, yes. However, I think that will quickly > become an issue for users who try to deploy erasure coding because those > group sizes will be quite large. As soon as we implement tiering, our > very next task - perhaps even before tiering gets into a release - > should be to implement automatic brick splitting. That will bring other > benefits as well, such as variable replication levels to handle the > sanlock case, or overlapping replica sets to spread a failed brick's > load over more peers. > OK. Do you have some initial ideas on how we could 'split' bricks? I ask this to see if I can work on splitting bricks while the data classification format is being ironed out. thanks, Krish _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-devel
