You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While looking into performance issues in one of our clusters I've noticed that the v4.17 Java driver does uses some sub-optimal queries on connecting to the cluster:
CompletionStage<AdminResult> localQuery = query(channel, "SELECT * FROM system.local");
Both of these queries force full table scan as there's no key reference. I've tried appending WHERE key = 'local' to these queries and as a result the Session creation got about 90 % faster in the troubled cluster case. (YMMV)
This seems to be fixed in the 3.x version of the driver.
While looking into performance issues in one of our clusters I've noticed that the v4.17 Java driver does uses some sub-optimal queries on connecting to the cluster:
java-driver/core/src/main/java/com/datastax/oss/driver/internal/core/channel/ProtocolInitHandler.java
Line 83 in d33dbc5
java-driver/core/src/main/java/com/datastax/oss/driver/internal/core/metadata/DefaultTopologyMonitor.java
Line 171 in d33dbc5
Both of these queries force full table scan as there's no key reference. I've tried appending
WHERE key = 'local'
to these queries and as a result the Session creation got about 90 % faster in the troubled cluster case. (YMMV)This seems to be fixed in the 3.x version of the driver.
java-driver/driver-core/src/main/java/com/datastax/driver/core/ControlConnection.java
Line 79 in 9fe1e03
Looks related to this issue.
The text was updated successfully, but these errors were encountered: