I've been experiencing some issues with the Java driver and I'm pretty sure someone here can help out. :-)
Apache Cassandra 3.11.4. Whenever a node crashes on disk failure (SSD), the Cassandra nodes identify it is down and from C* perspective, all is fine. However, the Java driver still "thinks" it is connected to the node and tries to get data from it until a queue is building up and creates a lag on the application level.
The driver version is 3.1, which I believe doesn't have a default retry policy that mitigates this issue (please correct me if I'm wrong). I've suggested the application teams to upgrade the driver to the latest version in order to prevent such issues from recurring and they'd like to get assured that the new driver will indeed not be affected from this.
Is my suggestion correct?
Is there a document that better explains this scenario and how the driver behaves in this case?
Thanks a lot!