Hi Bo,
I would suggest adding:
.withReconnectionPolicy(new ExponentialReconnectionPolicy(1000,3))
or something similar to your cluster builder.
Steve
On Wed, Mar 16, 2016 at 11:18 AM, Bo Finnerup Madsen wrote:
> Hi Sean,
>
> Thank you for taking the time to answer :)
> We are using a ve
Hi Sean,
Thank you for taking the time to answer :)
We are using a very vanilla connection, without any sorts of tuning
policies. The cluster/session is constructed as follows:
final Cluster cluster = Cluster.builder()
.addContactPoints(key.getContactPoints())
Hi,
I ran another test with the following client setup:
final Cluster cluster = Cluster.builder()
.addContactPoints(key.getContactPoints())
.withSocketOptions(new SocketOptions().setKeepAlive(true))
.withReconnectionPolicy(Policies.defaultReconnectionPolicy())
.withRetryPolicy(Policies.def
Hi Steve,
Thank you for the suggestion. I will try it now, and report back :)
Yours sincerely,
Bo
ons. 16. mar. 2016 kl. 19.23 skrev Steve Robenalt :
> Hi Bo,
>
> I would suggest adding:
>
> .withReconnectionPolicy(new ExponentialReconnectionPolicy(1000,3))
>
> or something similar to you
Are you using any of the Tuning Policies
(https://docs.datastax.com/en/developer/java-driver/2.0/common/drivers/reference/tuningPolicies_c.html)?
It could be that you are hitting some peak load and the driver is not retrying
hosts once they are marked “down.”
Sean Durity – Lead Cassandra Admin
Hi Bo,
You might try sending the same question to the java driver mailing list. I
haven't seen your particular error in several years of running Cassandra on
AWS. The closest I saw in the past was due to a protocol error in the
driver during the 2.0 beta timeframe.
Steve
On Wed, Mar 16, 2016 at
