An upstream bug would be ideal as github issue is mainly used for
enhancements. In the mean time, could you point to the exact failure shown
at the command line and the log entry from cli.log?
On Wed, Aug 23, 2017 at 12:10 AM, Serkan ?oban <cobanserkan at gmail.com>
wrote:
> Hi, I think this is the line limiting brick count:
> https://github.com/gluster/glusterfs/blob/c136024613c697fec87aaff3a07086
> 2b92c57977/cli/src/cli-cmd-parser.c#L84
>
> Can gluster-devs increase this limit? Should I open a github issue?
>
> On Mon, Aug 21, 2017 at 7:01 PM, Serkan ?oban <cobanserkan at
gmail.com>
> wrote:
> > Hi,
> > Gluster version is 3.10.5. I am trying to create a 5500 brick volume,
> > but getting an error stating that 4444 bricks is the limit. Is this a
> > known limit? Can I change this with an option?
> >
> > Thanks,
> > Serkan
> _______________________________________________
> 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/c651bcf9/attachment.html>