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

Hi, I'm looking forward to a patch (file) for this bug(CASSANDRA-11344) to apply C* version 2.2.5. Is there available patch for that version? I watched link(https://issues.apache.org/jira/browse/CASSANDRA-11344) but couldn't find patch file or something like that. Or is there any workaround to

Cassandra 2.0.x OOM during bootstrap

Hi, all, We have recently encountered a Cassandra OOM issue when Cassandra is brought up sometimes (but not always) in our 4-node cluster test bed. After analyzing the heap dump, we could find the Internal-Response thread pool (JMXEnabledThreadPoolExecutor) is filled with thounds of

Optional TLS CQL Encryption

Hey Guys, Is there a way to make TLS encryption optional for the CQL listener? We'd like to be able to use for remote management connections but not for same datacenter usage (since the build/up tear down cost is too high for things that don't use pools). Right now it appears if we enable

Re: Proper use of COUNT

Sylvain & Tyler, this Jira is for a user reporting a timeout for SELECT COUNT(*) using 3.3: https://issues.apache.org/jira/browse/CASSANDRA-11566 I'll let one of you guys follow up on that. I mean, I thought it was timing out die to the amount of data, but you guys are saying that paging should

nodetool -h fails Connection refused

Hi, I am trying to run nodetool remotely. but its not working: I am running Cassandra 2.2.5 on CentOS 6. listen_address: is set to rpc_address: is set to 0.0.0.0 broadcast_rpc_address: is set to I changed the following in cassadnra-env.sh JVM_OPTS="$JVM_OPTS -Djava.rmi.server.hostname="

Re: Discrepancy while paging through table, and static column updated inbetween

This sounds similar to https://issues.apache.org/jira/browse/CASSANDRA-10010, but that only affected 2.x. Can you open a Jira ticket with your table schema, the problematic query, and the details you posted here? On Tue, Apr 19, 2016 at 10:25 AM, Siddharth Verma < verma.siddha...@snapdeal.com>

Re: Proper use of COUNT

Thanks, Tyler. "Deduping (i.e. normal conflict resolution) happens per-page" Are the queries sent from the coordinator to other nodes sequencing through partitions in token order and that's what allows the coordinator to dedupe with just a single page at a time? IOW, if a target node responds

Re: Proper use of COUNT

On Tue, Apr 19, 2016 at 9:51 AM, Jack Krupansky wrote: > > 1. Another clarification: All of the aggregate functions, AVG, SUM, MIN, > MAX are in exactly the same boat as COUNT, right? > Yes. > > 2. Is the paging for COUNT, et al, done within the coordinator node? >

Re: Traffic inconsistent across nodes

Glad that worked out, that was going to be my next suspicion, since everything thought it was up and happy, I can't think of a way that Cassandra and the driver could both consider the cluster happy if some nodes were not transmitting at least some data (they have to at least for gossip). On Mon,

Discrepancy while paging through table, and static column updated inbetween

Hi, We are using cassandra(dsc3.0.3) on production. For some purpose, we were doing a full table scan (setPagingState and getPagingState used on ResultSet in java program), and there has been some discrepancy when we ran the same job multiple times. Each time some new data was added to the

Re: Proper use of COUNT

Thanks for that clarification, Sylvain. 1. Another clarification: All of the aggregate functions, AVG, SUM, MIN, MAX are in exactly the same boat as COUNT, right? 2. Is the paging for COUNT, et al, done within the coordinator node? 3. Does dedupe on the coordinator node consume memory

Re: Proper use of COUNT

> > > Accept for relatively small or narrow queries, it seems to have a > propensity for timing out. > For recent enough version of C*, it shouldn't since it pages internally (it will be slow and as always be, but it shouldn't time out if some decent page size is used, which should be the

Re: Bootstrapping Question for Cassandra 2.0

It will be possible after the tokens reassignment has finished. Actually Cassandra itself will tell you. If you try the remove command and is not possible it will fail with an error indicating that the operation is not possible while there are nodes in Joining status. Regards Carlos Alonso |