Nitin Chhabra created CASSANDRA-19388:
-----------------------------------------
Summary: Incorrect connected node metric when session is closed
and reinitted in same JVM
Key: CASSANDRA-19388
URL: https://issues.apache.org/jira/browse/CASSANDRA-19388
Project: Cassandra
Issue Type: Bug
Components: Client/java-driver
Reporter: Nitin Chhabra
Assignee: Henry Hughes
We observed incorrect connected nodes metric reported when session is closed
and re-initted.
*Setup*
Java 8
Java Driver Version: 4.15.0
Cassandra Server: 4.X
3 nodes in Azure West
*Steps to reproduce the issue*
# Init the CQLSession successfully.
# Observe the connected nodes metric is 3.
# Stop the session gracefully by calling: session.closeAsync() and wait for
few seconds for close.
# _Reinit the CQLSession and monitor the connected nodes metric. It goes down
to 1._
*Triage/Troubleshooting*
On Cassandra Server side, we can observe connections made to all 3 nodes. Upon
further debugging by putting some log statements and modifying the driver, it
appears the NodeStateManager updates its open connection count to 3, however
MetaDataManager does not show all 3 nodes have active connections. Please let
me know if more info is needed.
Also, had initiated similar discussion in Open Src Community:
[https://groups.google.com/a/lists.datastax.com/g/java-driver-user/c/VoPOha4Oc0c/m/IDCVAREMAgAJ?utm_medium=email&utm_source=footer|https://urldefense.com/v3/__https://groups.google.com/a/lists.datastax.com/g/java-driver-user/c/VoPOha4Oc0c/m/IDCVAREMAgAJ?utm_medium=email&utm_source=footer__;!!IfjTnhH9!XpuIqw-OxNBAy2e4AVXzpwJwHST0C5CevI9NQGMGp54QUFPJGFCt5PZF527PRMYABto_Dwk03Pwb1dNSEgcLatnsOQ$].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
