Bringing together the Apache Cassandra experts from the community and DataStax.

Want to learn? Have a question? Want to share your expertise? You are in the right place!

Not sure where to begin? Getting Started

 

question

NiD avatar image
NiD asked ·

Using spring-data-cassandra, what does "Failed to connect with protocol DSE_V2" mean?

Hello,

I came across these logs and found curious what these mean which i marked in bold while am building my project . Did i miss something, It would be great if someone can explain me what does this mean.

And I tried different Protocol Version by extending AbstractCassandraConfiguration but nothing changed.

For more info these are the version which I am running.

  • Cassandra - 3.11.6
  • Spring Boot - 2.3.1
2020-07-23 22:44:28.559 INFO 24543 --- [ main] c.d.o.d.i.core.DefaultMavenCoordinates : DataStax Java driver for Apache Cassandra(R) (com.datastax.oss:java-driver-core) version 4.6.1
2020-07-23 22:44:29.002 INFO 24543 --- [ s0-admin-0] c.d.oss.driver.internal.core.time.Clock : Using native clock for microsecond precision
2020-07-23 22:44:29.115 INFO 24543 --- [ s0-io-0] c.d.o.d.i.core.channel.ChannelFactory : [s0] Failed to connect with protocol DSE_V2, retrying with DSE_V1
2020-07-23 22:44:29.117 INFO 24543 --- [ s0-io-1] c.d.o.d.i.core.channel.ChannelFactory : [s0] Failed to connect with protocol DSE_V1, retrying with V4
2020-07-23 22:44:29.123 INFO 24543 --- [ s0-io-2] c.d.oss.driver.api.core.uuid.Uuids : PID obtained through native call to getpid(): 24543
2020-07-23 22:44:29.316 INFO 24543 --- [ s1-admin-0] c.d.oss.driver.internal.core.time.Clock : Using native clock for microsecond precision 2020-07-23 22:44:29.319 INFO 24543 --- [ s1-io-0] c.d.o.d.i.core.channel.ChannelFactory : [s1] Failed to connect with protocol DSE_V2, retrying with DSE_V1
2020-07-23 22:44:29.321 INFO 24543 --- [ s1-io-1] c.d.o.d.i.core.channel.ChannelFactory : [s1] Failed to connect with protocol DSE_V1, retrying with V4
2020-07-23 22:44:29.692 INFO 24543 --- [ main] c.v.a.VkDigitalAnalyticsApplicationTests : Started VkDigitalAnalyticsApplicationTests in 1.987 seconds (JVM running for 2.712) [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.425 s - in com.viewway.analytics.VkDigitalAnalyticsApplicationTests
2020-07-23 22:44:31.858 WARN 24543 --- [ s0-admin-0] c.d.o.d.i.core.session.DefaultSession : [s0] Error while closing com.datastax.oss.driver.internal.core.config.typesafe.DefaultDriverConfigLoader@6c5a991c (RejectedExecutionException: event executor terminated)
spring-data-cassandra
10 |1000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

1 Answer

Erick Ramirez avatar image
Erick Ramirez answered ·

[UPDATED] With the updated log entries you posted, I see now that the right version is being used. The messages are logged at INFO level since they're for informational purposes only.

The driver attempts to negotiate with DSE_V2 protocol to see if the cluster is running on a newer versions of DSE (6.0 or newer) then tries to connect with DSE_V1 for DSE 5.1 (see DseProtocolVersion.java). Finally, it settles on Cassandra native protocol V4 (C* 2.2+, CASSANDRA-8043).

To be clear, there isn't a problem here and there's nothing to worry about.

For some background info, the drivers were previously "split" such that there were 2 different forks:

  • dse-java-driver - a Java client for DataStax Enterprise designed to only work with DSE and had access to DSE-only features such as DSE Graph.
  • java-driver - a Java client for open-source Apache Cassandra.

In January 2020, we announced that we have unified the drivers into one to make it simple for users (see Chris Splinter's blog post Better Drivers for Cassandra). From Java driver 4.4.0, there is just one version to use to connect to any cluster -- DSE, OSS Cassandra, DataStax Astra. Cheers!

1 comment Share
10 |1000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

First of all thank you for the reply and I want to mention one thing, the only dependency which i used for cassandra is "spring-boot-starter-data-cassandra". I think by default its using "(com.datastax.oss:java-driver-core) version 4.6.1" , which we can see that from the above logs.

As you said i also tried with dependency which you suggested but i got the same in logs as above.

0 Likes 0 · ·