search for: callpool

Hello, I found a new issue with glusterfs 3.2.1 - im getting a glusterfs process for each mountpoint and they are consuming all of the CPU time. strace won't show a thing - so no system calls are made Mounting the same volumes on another server works fine. Has anyone seen such a thing? Oder any idea, what causes this and how to fix it? The logfiles don't show any information about

I do not mean to be argumentative, but I have to admit a little frustration with Gluster. I know an enormous emount of effort has gone into this product, and I just can't believe that with all the effort behind it and so many people using it, it could be so fragile. So here goes. Perhaps someone here can point to the error of my ways. I really want this to work because it would be ideal

Hi We're seeing high? number of pending calls on two of our glusterfs 3.10 clusters. We have not tried to tune anything except changing server.event-threads: 2 gluster volume status callpool | grep Pending results in various numbers but more often that not a fair few of the bricks have 200-400 pending calls. Is there a way I can debug this further? The servers are 8x dual 8 core with 64G memory running a distributed cluster with 4 bricks on each. The four glusterfsd processes are ave...