Hi, A discussion has arisen in the gocql team about how to handle saturation when CQL clients are sending in packets at a faster rate than the Cassandra cluster can sustain.
What is the general approach to this from a server perspective? Is there any flow control that the server can apply to back pressure onto the sending driver? If this were the case, you could code the driver to propagate this back pressure onto the sending app. If not, how do other driver implementors view this situation? Do you try to maintain some kind of flow control at the driver level so that you can push back onto the app, or you just let the effects of IO saturation just bubble up to the app? Cheers, Ben
