It depends on your workload and expectations. I have 1500 bricks in single volume and happy with it. I don't do metadata heavy operations on it. I also 4000 bricks single volume in plan if it pass the evaluations. Just do your tests and make sure it works before going production. On Mon, Mar 6, 2017 at 11:54 AM, qingwei wei <tchengwee@xxxxxxxxx> wrote: > Hi Serkan, > > Thanks for the information. So 150 bricks should still be good. So > what number of bricks is consider excessive? > > Cw > > On Mon, Mar 6, 2017 at 3:14 PM, Serkan Çoban <cobanserkan@xxxxxxxxx> wrote: >> Putting lots of bricks in a volume have side affects. Slow meta >> operations, slow gluster commands executions, etc. >> But 150 bricks are not that much. >> >> On Mon, Mar 6, 2017 at 9:41 AM, qingwei wei <tchengwee@xxxxxxxxx> wrote: >>> Hi, >>> >>> Is there hard limit on the maximum number of bricks per Gluster >>> volume. And if no such hard limit exists, then is there any best >>> practice on selecting the number of bricks per volume. Example, if i >>> would like to create a 200TB for my host, which config below is >>> better? >>> >>> HDD: 4TB (1 brick on 1 physical disk) >>> 1 Gluster volume = 10x3 (30 bricks in total) >>> total 5 Gluster volumes are created and host will combine them as one >>> logical volume >>> >>> or >>> >>> HDD: 4TB (1 brick on 1 physical disk) >>> 1 Gluster volume = 50x3 (150 bricks in total) >>> total 1 Gluster volume is created >>> >>> >>> Thanks. >>> >>> Cw >>> _______________________________________________ >>> 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
