We're using glusterfs in Amazon EC2 and observing certain behavior involving EBS volumes. The basic situation is that, in some cases, clients can write data to the file system at a rate such that the gluster daemon on one or more of the nodes may block in disk wait for longer than 42 seconds, causing gluster to decide that the brick is down. In fact, it's not down, it's just slow. I believe it is possible by looking at certain system data to tell the difference from the system with the drive on it between down and working through its queue. We are attempting a two-pronged approach to solving this problem: 1. We would like to figure out how to tune the system, including either or both of adjusting kernel parameters or glusterd, to try to avoid getting the system into the state of having so much data to flush out to disk that it blocks in disk wait for such a long time. 2. We would like to see if we can make gluster more intelligent about responding to the pings so that the client side is still getting a response when the remote side is just behind and not down. Though I do understand that, in some high performance environments, one may want to consider a disk that's not keeping up to have failed, so this may have to be a tunable parameter. We have a small team that has been working on this problem for a couple of weeks. I just joined the team on Friday. I am new to gluster, but I am not at all new to low-level system programming, Linux administration, etc. I'm very much open to the possibility of digging into the gluster code and supplying patches if we can find a way to adjust the behavior of gluster to make it behave better under these conditions. So, here are my questions: * Does anyone have experience with this type of issue who can offer any suggestions on kernel parameters or gluster configurations we could play with? We have several kernel parameters in mind and are starting to measure their affect. * Does anyone have any background on how we might be able to tell that the system is getting itself into this state? Again, we have some ideas on this already, mostly by using sysstat to monitor stuff, though ultimately if we find a reliable way to do it, we'd probably code it directly by looking at the relevant stuff in /proc from our own code. I don't have the details with me right now. * Can someone provide any pointers to where in the gluster code the ping logic is handled and/or how one might go about making it a little smarter? * Does my description of what we're dealing with suggest that we're just missing something obvious? I jokingly asked the team whether they had remembered to run glusterd with the --make-it-fast flag, but sometimes there are solutions almost like that that we just overlook. For what it's worth, we're running gluster 3.8 on CentOS 7 in EC2. We see the problem the most strongly when using general purpose (gp2) EBS volumes on higher performance but non-EBS optimized volumes where it's pretty easy to overload the disk with traffic over the network. We can mostly mitigate this by using provisioned I/O volumes or EBS optimized volumes on slower instances where the disk outperforms what we can throw at it over the network. Yet at our scale, switching to EBS optimization would cost hundreds of thousands of dollars a year, and running slower instances has obvious drawbacks. In the absence of a "real" solution, we will probably end up trying to modify our software to throttle writes to disk, but having to modify our software to keep from flooding the file system seems like a really sad thing to have to do. Thanks in advance for any pointers! --Jay _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
