Open djMax opened 7 years ago
I have some suspicion this is a version problem. Should wasabi work with the latest protocol?
@djMax Were you able to get it working with 3 nodes cluster by any chance? I am trying the same thing and having issues. Also, could you please share how you specified 3 nodes in pom.xml if possible?
In the end, we gave up on wasabi and built our own. In large part because we're a postgres/elastic search shop and I didn't want to have to maintain mysql/cassandra just for this.
I'm getting this error in Kubernetes on Azure as well.
Edit: I'm actually running into this issue running any dockerized version of the application that isn't installed via the shell scripts.
Yeah, I've tried a ton of things here.
I'm still stuck as I can manually cqlsh from my mac to the cluster, and I can use cqlsh once accessed into a shell in the Cassandra instance but Wasabi is failing to connect. Likely going to have to look at other solutions but disappointed as I've been impressed with the offering.
Has anyone managed to solve this? I have the same issue with Cassandra 3.11 and drivers 3.5.0
Managed to solve this.
The reason behind is Cassandra driver built by Datastax and the way it is used in the Wasabi application. There is LoadBalancingPolicy set in DefaultCassandraDriver.java:104. DCAwareRoundRobinPolicy doesn't work with more than one node. If set to TokenAwarePolicy then it works with multiple nodes. "Works" here means that I am able to start application, create experiments manipulate data and real time APIs. Changing the policy might cause other issues for loadbalancing/cluster, I don't know yet...
The real problem is that cassandra uses the cassandra DataCenter name, and if that doesn't match, it cannot connect, this is why it says 3 available, no hosts tried. Wasabi is tring to found hosts of cassandra with the specified DataCenter name.
The docs on this could be a lot better. I'm getting gobs of this error trying to use a 3 node cassandra cluster in Kubernetes on aws: