Observed driver throwing ClosedConnectionException when it shouldn't?

[Jestin Ma]

When restarting a node in a cluster with replication factor 3, I observed ClosedConnectionException being thrown because there was an error with the Netty IO channel:

Caused by: com.datastax.oss.driver.api.core.connection.ClosedConnectionException: Unexpected error on channel
Caused by: java.io.IOException: Connection reset by peer

The error is understandable since I brought down some node. However, shouldn't the driver retry all coordinators before throwing a AllNodesFailedException containing this exception, as it says so in the documentation?

I believe the error is thrown/interpreted in InFlightHandler. Am I misunderstanding something about why this error is being thrown?

Thanks.

Jestin

[Jestin Ma]

Upon more reading, it might be because the retry policy doesn't kick in if the query isn't idempotent.