Working With Prepared Statements

Hi Everyone, I want to start working with Prepared Statements. I've read https://docs.datastax.com/en/developer/java-driver/3.1/manual/statements/prepared/ and just wanted to know if there are any other considerations I need to take into account when deciding to use Prepared Statements. Thanks!

Do not use Cassandra 3.11.0+ or Cassandra 3.0.12+

Hello, Current latest Cassandra version (3.11.0, possibly also 3.0.12+) has a race condition that causes Cassandra to create broken sstables (stats file in sstables to be precise). Bug described here: https://issues.apache.org/jira/browse/CASSANDRA-13752 This change might be causing it (but not

Cassandra and OpenJDK

Hi, We're using Cassandra 3.0.9. I've found some warnings that Cassandra should not be deployed using OpenJDK, but all the information on that is at least 2 years old. Is this still something to watch out for? Or is the warning just legacy? Thanks, Myrle Krantz Solution Architect, Kuelap, Inc.

Re: Cassandra and OpenJDK

On Mon, Aug 28, 2017 at 9:00 AM, Myrle Krantz wrote: > Hi, > > We're using Cassandra 3.0.9. I've found some warnings that Cassandra > should not be deployed using OpenJDK, but all the information on that > is at least 2 years old. > > Is this still something to watch out for? Or is the warning

Re: Cassandra and OpenJDK

OpenJDK is fine.

Conection refuse

Hi, I am getting an error connecting to cqlsh. I am getting the following error. Connection error: ('Unable to connect to any servers', {'127.0.0.1': error(111, "Tried connecting to [('127.0.0.1', 9042)]. Last error: Connection refused")}) I change the Cassandra.yaml file setting for rpc_address

Re: Conection refuse

Is this a local install? If so you can set your rpc_address to 127.0.0.1. The rpc_address are the IP addresses that will be allowed to make connections to Cassandra. I suspect the problem is that you have set your RPC address to your IP address with is different from 127.0.0.1. cqlsh by defau

Re: Do not use Cassandra 3.11.0+ or Cassandra 3.0.12+

We're using 3.0.12+ for a few months and haven't seen the issue like that. Do we know what could trigger the problem? Or is 3.0.x really impacted? Thanks, Jay On 8/28/17 6:02 AM, Hannu Kröger wrote: > Hello, > > Current latest Cassandra version (3.11.0, possibly also 3.0.12+) has a race > condit

Re: Do not use Cassandra 3.11.0+ or Cassandra 3.0.12+

For what it's worth, I don't think this impacts 3.0 without adding some other code change (the reporter of the bug on 3.0 had added custom metrics that exposed a concurrency issue). We're looking at it on 3.11. I think 13038 made it far more likely to occur, but I think it could have happened p

Re: Do not use Cassandra 3.11.0+ or Cassandra 3.0.12+

I shouldn't actually say I don't think it can happen on 3.0 - I haven't seen this happen on 3.0 without some other code change to enable it, but like I said, we're still investigating. -- Jeff Jirsa > On Aug 28, 2017, at 8:30 PM, Jeff Jirsa wrote: > > For what it's worth, I don't think thi