On 11/13/2014 12:11 PM, Atin Mukherjee wrote: > > > On 11/09/2014 10:31 PM, Atin Mukherjee wrote: >> >> >> On 11/08/2014 05:21 AM, Justin Clift wrote: >>> On Wed, 05 Nov 2014 14:58:06 +0530 >>> Atin Mukherjee <amukherj@xxxxxxxxxx> wrote: >>> <snip> >>>> Can there be any cases where glusterd instance may go down >>>> unexpectedly without a crash? >>>> >>>> [1] http://build.gluster.org/job/rackspace-regression-2GB-triggered >>>> /2319/consoleFull >>> >>> Has anyone gotten back to you about this? >>> >> Not yet :( >> >> ~Atin > Though we don't have the exact clue why the first glusterd instance > stopped responding, but looking at the current test case I attempted to > make this more safe in terms of cli failures in > http://review.gluster.org/#/c/9114/ > > Also currently we do not have per instance cli log file unlike we have > for glusterd in cluster setup. http://review.gluster.org/#/c/9100/ > should ensure cli.log files are created per cli instances. > > ~Atin I see the mgmt locks spurious-failure-fix patches referenced above have been merged but I am still able to hit it on master. In case some motivated soul wants to have a look, here is the log: http://build.gluster.org/job/rackspace-regression-2GB-triggered/2961/consoleFull >>> + Justin >>> >> _______________________________________________ >> Gluster-devel mailing list >> Gluster-devel@xxxxxxxxxxx >> http://supercolony.gluster.org/mailman/listinfo/gluster-devel >> > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxxx > http://supercolony.gluster.org/mailman/listinfo/gluster-devel > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-devel
