On 12/01/2015 04:15 AM, Andrus, Brian Contractor wrote: > All, > > > > I am seeing it VERY consistently that when I do a ‘gluster peer status’ > or ‘gluster pool list’, the system ‘hangs’ for up to 1 minute before > spitting back results. That's interesting, 'gluster peer status' or 'pool list' is a local node operation and doesn't incur RPC calls. Until and unless it takes time to communicate back to CLI because of a poor N/W, I don't see any reason why would it take such a long time. Can you run glusterd with debug log enabled and share the *glusterd.log file with us? ~Atin > > > > I have 10 nodes all on the same network and currently ZERO volumes or > bricks configured. Just trying to get good performance for the cluster > to be talking to itself…. > > > > > > What is gluster doing that takes so long to respond? Seems there may be > a more efficient way of doing it, whatever it is… > > > > > > > > Brian Andrus > > ITACS/Research Computing > > Naval Postgraduate School > > Monterey, California > > voice: 831-656-6238 > > > > > > > > _______________________________________________ > Gluster-users mailing list > Gluster-users@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-users > _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
