Hello, as per http://gluster.org/pipermail/gluster-users/2011-May/007788.html I am advised to use bricks which are uniform in size, but for a number of reasons this is not possible at the moment in my current setup. So the question is: what is the expected behaviour when two bricks with different sizes are coupled to form a replica? Will the larger brick keep accepting writes even after the smallest brick has been filled up? In this scenario, what conditions become relevant in the process of rebalancing a volume? Is there a precedence of the first brick in a replica (as per volume definition)? Thank you very much in advance for your attention, Best regards
On Mon, Aug 13, 2012 at 06:03:36PM +0200, s19n wrote:> So the question is: what is the expected behaviour when two bricks > with different sizes are coupled to form a replica? Will the larger > brick keep accepting writes even after the smallest brick has been > filled up?I haven't tested, but I'd expect ENOSPC when the smaller one files up. I'd be inclined to split the larger server into two volumes: one the same size as the smaller server, to form a replica set, and put the remaining space in a single-volume brick for use as scratch space, backups, or whatever. Regards, Brian.