Re: Changing Racks of Nodes

If the rack as defined in Cassandra stays the same (e.g. cassandra-rackdc.properties), things will keep working as expected... except when the actual rack (or fault domain) goes down and you are likely to lose more nodes than expected. If you change the rack as defined in Cassandra, the node will

Changing Racks of Nodes

Hello, If a running node moves around and changes its rack in the process, when its back in the cluster (through ignore-rack property), is it a correct statement that queries will not see some data residing on this node until a repair is run ? Or, is it more like the node may get requests for

Re: When are hints written?

how do you unsubscribe From: Bo Finnerup Madsen Sent: Wednesday, April 20, 2016 9:38 AM To: user@cassandra.apache.org Subject: When are hints written? Hi, We have a small 5 node cluster of m4.xlarge clients that receives writes from

Re: nodetool -h fails Connection refused

Thanks Nate... It works now.. On Wed, Apr 20, 2016 at 8:05 AM, Nate McCall wrote: > You need to set LOCAL_JMX=false > > It will then read the rest of this stanza: > > https://github.com/apache/cassandra/blob/cassandra-2.2/conf/cassandra-env.sh#L284-L288 > > Using the

Re: A few misbehaving nodes

Can you show the output of a tpstats on one of the effected nodes? That will give some indication where the trouble might be. Patrick On Tue, Apr 19, 2016 at 6:54 AM, sai krishnam raju potturi < pskraj...@gmail.com> wrote: > hi; >do we see any hung process like Repairs on those 3 nodes?

Limit 1

I have a following table(using default sized tier compaction) that its column get TTLed every hour(as we want to keep only the last 1 hour events) And I do Select * from mytable where object_id = ‘’ LIMIT 1; And since query only interested in last/latest value, will cassandra need to scan

Re: Cassandra causing OOM Killer to strike on new cluster running 3.4

Hi, Paulo Thank you for your help! I'll try to use it. Regards, Satoshi On Wed, Apr 20, 2016 at 8:43 PM, Paulo Motta wrote: > 2.2.6 should be released in the next couple of weeks, but I also attached > a patch file to the issue if you want to patch 2.2.5 manually. >

Re: When are hints written?

Hi Bo, > In our case, I would like for the cluster to wait for the write to be persisted on the relevant nodes before returning an ok to the client. But I don't know which knobs to turn to accomplish this? or if it is even possible :) This is what write consistency option is for. Have a look at

Re: nodetool -h fails Connection refused

You need to set LOCAL_JMX=false It will then read the rest of this stanza: https://github.com/apache/cassandra/blob/cassandra-2.2/conf/cassandra-env.sh#L284-L288 Using the defaults above as-is, you will need to add JMX authentication. Details are here:

When are hints written?

Hi, We have a small 5 node cluster of m4.xlarge clients that receives writes from ~20 clients. The clients will write as fast as they can, and the whole process is limited by the write performance of the cassandra cluster. After we have tweaked our schema to avoid large partitions, the load is

Re: Cassandra causing OOM Killer to strike on new cluster running 3.4

2.2.6 should be released in the next couple of weeks, but I also attached a patch file to the issue if you want to patch 2.2.5 manually. 2016-04-20 0:19 GMT-03:00 Satoshi Hikida : > Hi, > > I'm looking forward to a patch (file) for this bug(CASSANDRA-11344) to > apply

Re: Optional TLS CQL Encryption

Hi Sam, That's exactly what I was hoping for, but couldn't find in the docs. Thank you very much! -J Sent via iPhone > On Apr 20, 2016, at 02:05, Sam Tunnicliffe wrote: > > From 3.0, separate ports can be configured for encrypted & non-encrypted > connections. > See

Re: Optional TLS CQL Encryption

>From 3.0, separate ports can be configured for encrypted & non-encrypted connections. See https://issues.apache.org/jira/browse/CASSANDRA-9590 On Wed, Apr 20, 2016 at 8:51 AM, Jason J. W. Williams < jasonjwwilli...@gmail.com> wrote: > Hi Ben, > > Thanks for confirming what I saw occur. The

Re: Optional TLS CQL Encryption

Hi Ben, Thanks for confirming what I saw occur. The Datastax drivers don't play very nicely with Twisted Python so connection pooling is inconsistent and makes always-on TLS a no-go performance-wise. The encryption overhead isn't the problem, it's the build-up of the TLS session for every

Re: Optional TLS CQL Encryption

Hi Jason If you enable encryption it will be always on. Optional encryption is generally a bad idea (tm). Also always creating a new session every query is also a bad idea (tm) even without the minimal overhead of encryption. If you are really hell bent on doing this you could have a node that