On Fri, 6 Oct 2017 at 19:05, Michael Scherer wrote:
> Le vendredi 06 octobre 2017 à 16:53 +0530, Gaurav Yadav a écrit :
> > As gluster cli was failing to create a volume which has tons of brick
> > request in one command.
> > I added this https://review.gluster.org/#/c/18271/5/tests/bugs/cli/bu
>
Le vendredi 06 octobre 2017 à 16:53 +0530, Gaurav Yadav a écrit :
> As gluster cli was failing to create a volume which has tons of brick
> request in one command.
> I added this https://review.gluster.org/#/c/18271/5/tests/bugs/cli/bu
> g-
> 1490853.t test to ensure that
> gluster is able to pars
As gluster cli was failing to create a volume which has tons of brick
request in one command.
I added this https://review.gluster.org/#/c/18271/5/tests/bugs/cli/bug-
1490853.t test to ensure that
gluster is able to parse large request.
As per the bug "https://bugzilla.redhat.com/show_bug.cgi?id=14
Hi,
so on the last 2 days, I have been contacted by people because some
builders were failling. Upon investigation ( https://bugzilla.redhat.co
m/show_bug.cgi?id=1498390 ), the main issue seems to be the following:
Each build failed had a set of glusterd process (around 300) that where
started by
