[Gluster-users] Brick count limit in a volume

[Gaurav Yadav]

In your case for 5500 bricks cli is failing the command saying "Total brick
list is larger than a request. Can take (brick_count 4444)".

RCA..
gluster cli while parsing the command takes the wordcount and based on that
it compares the statically initialized size as you have point out in
https://github.com/gluster/glusterfs/blob/c136024613c697fec87aaff3a07086
2b92c57977/cli/src/cli-cmd-parser.c#L84.
<https://github.com/gluster/glusterfs/blob/c136024613c697fec87aaff3a070862b92c57977/cli/src/cli-cmd-parser.c#L84>
While doing so when
wordcount increases which is happening in your case cli fails the command
with the above message.
In the error message you are getting 4444, this is coming based on the
parsing logic.

I believe having dynamically allocated size based on max_brick_path(4096) *
no_of_bricks will solve the issue.

Thanks
Gaurav

On Wed, Aug 23, 2017 at 11:23 AM, Serkan Çoban <cobanserkan at gmail.com>
wrote:

> This is the command line output:
> Total brick list is larger than a request. Can take (brick_count 4444)
> Usage: volume create <NEW-VOLNAME> [stripe <COUNT>] [replica <COUNT>] ....
>
> I am testing if a big single volume will work for us. Now I am
> continuing testing with three volumes each 13PB...
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20170823/2ff767ee/attachment.html>