Streaming from 1 node only when adding a new DC

Hello, We've tested adding a new DC from an existing DC having 3 nodes and RF=3 (ie all nodes have all data). During the rebuild process, only one node of the first DC streamed data to the 3 nodes of the second DC. Our goal is to minimise the time it takes to rebuild a DC and would like to be

Why there is no native shutdown command in cassandra

Hi All Why we dont have native shutdown command in Cassandra ? Every software provides graceful shutdown command. ​Regards, Anshu​

Re: Why there is no native shutdown command in cassandra

`nodetool drain` From: Anshu Vajpayee Reply-To: "user@cassandra.apache.org" Date: Monday, June 13, 2016 at 9:28 AM To: "user@cassandra.apache.org" Subject: Why there is no native shutdown command in cassandra

Re: Why there is no native shutdown command in cassandra

Thanks, I am able to run the stopdaemon option in version 2.1. but it doesn't print anything in log for log level INFO about shutdown. In case of log level DEBUG , it prints shutdown information. INFO [RMI TCP Connection(4)-127.0.0.1] 2016-06-13 09:49:29,223 CassandraDaemon.java:410 - Cassandra

Installing Cassandra from Tarball

I am trying out Cassandra and have installed it on a single Amazon Linux AMI instance (. I downloaded the Cassandra 3.6 tarball. However when I run Cassandra I notice there are the following warnings: WARN 15:41:58 Small commitlog volume detected at /var/lib/cassandra/commitlog; setting

Re: Why there is no native shutdown command in cassandra

Thanks for information. Does stopdaemon also flush memtables and stop trift and CQL interface before shutting down the daemon ? does node also announce shutting down message in ring ? On Mon, Jun 13, 2016 at 10:14 PM, Jake Luciani wrote: > If you want to understand why,

Re: Why there is no native shutdown command in cassandra

Yeah same as drain. Just exits at the end. On Mon, Jun 13, 2016 at 1:11 PM, Anshu Vajpayee wrote: > Thanks for information. > > Does stopdaemon also flush memtables and stop trift and CQL interface > before shutting down the daemon ? does node also announce

Tick Tock version numbers

I have a small, 3 machine, cluster with 3.2.1 Can I upgrade them to 3.6 from 3.2? Or is it advisable to upgrade to each intermediary version? Based on what I have gather seems like it is matter of: bring node down install new version bring up run nodetool upgradesstables -a Is that the

Re: select query on entire primary key returning more than one row in result

No, all rows were not the same. Querying only on the partition key gives 20 rows. In the erroneous result, while querying on partition key and clustering key, we got 16 of those 20 rows. And for "*tombstone_threshold"* there isn't any entry at column family level. Thanks, Siddharth Verma

Re: Why there is no native shutdown command in cassandra

If that's true it's a bug then. can you open a ticket and include the logs? https://issues.apache.org/jira/browse/CASSANDRA On Mon, Jun 13, 2016 at 2:19 PM, Anshu Vajpayee wrote: > I just tested. It doesn't flush memtables like nodetool drain/flush > command. Means it

Re: java.lang.OutOfMemoryError: Java heap space

Hi Ben, We're using the akka persistence layer which doesn't give me much scope for remodelling data. So, on the assumption that the guys who wrote the persistence layer knew what they were doing, I followed your suggestion to increase RAM (still only to a miserly 8gig, which the startup

Re: Why there is no native shutdown command in cassandra

I just tested. It doesn't flush memtables like nodetool drain/flush command. Means it only does crash for the node, no graceful shutdown. On Mon, Jun 13, 2016 at 10:51 PM, Jake Luciani wrote: > Yeah same as drain. Just exits at the end. > > On Mon, Jun 13, 2016 at 1:11 PM,

Re: select query on entire primary key returning more than one row in result

Running nodetool compact fixed the issue. Could someone help out as why it occurred.

select query on entire primary key returning more than one row in result

Hi, We are facing this issue on production, We upgraded our cassandra from 3.0.3 to 3.5 When we ran a query with partition key and clustering column(entire primary key specified), we get 16 rows in return. We have 2DC's, each with RF 3 for our keyspace. 1. We connected with cqlsh, and setting

Re: Why there is no native shutdown command in cassandra

As per Documentation(pasted as below), It does not stop Daemon . I tested also.I was looking for graceful shutdown for Cassandra Daemon.Description Flushes all memtables from the

Re: Why there is no native shutdown command in cassandra

If you want to understand why, it's because C* was designed to be crash-only. https://www.usenix.org/conference/hotos-ix/crash-only-software Since this is great for the project but bad for operators experience we have later added this stopdaemon command. On Mon, Jun 13, 2016 at 12:37 PM, Anshu

How to print out the metrics information, like compaction and garbage collection?

Hi there, I've deployed 6 node in Amazon EC2. I'm trying to monitor some metrics for each node and print them out when I write/read data into Cassandra. Specifically I want to print out the information about garbage collection and compaction. I do notice that there's metrics for

Re: Why there is no native shutdown command in cassandra

In Cassandra 3.x, I think there is a "nodetool stopdaemon" command On Mon, Jun 13, 2016 at 6:28 PM, Anshu Vajpayee wrote: > Hi All > > Why we dont have native shutdown command in Cassandra ? > > Every software provides graceful shutdown command. > > > > ​Regards, >

Re: select query on entire primary key returning more than one row in result

were all rows same? If not what was different ? What was droppable tombstone compaction ratio for that table/CF? On Mon, Jun 13, 2016 at 6:11 PM, Siddharth Verma < verma.siddha...@snapdeal.com> wrote: > Running nodetool compact fixed the issue. > > Could someone help out as why it occurred. >

Re: Installing Cassandra from Tarball

Hi Steve, Please find the responses in line: WARN 15:41:58 Unable to lock JVM memory (ENOMEM). This can result in part > of the JVM being swapped out, especially with mmapped I/O enabled. Increase > RLIMIT_MEMLOCK or run Cassandra as root. > You can edit -* /etc/security/limits.conf *and put

Spark Memory Error - Not enough space to cache broadcast

Hi, I'm using spark 1.5.1 version. I am reading data from Kafka into Spark and writing it into Cassandra after processing it. Spark job starts fine and runs all good for some time until I start getting below errors. Once these errors come, job start to lag behind and I see that job has scheduling

Re: Why there is no native shutdown command in cassandra

https://issues.apache.org/jira/browse/CASSANDRA-12001 for your reference. On Mon, Jun 13, 2016 at 11:55 PM, Jake Luciani wrote: > If that's true it's a bug then. can you open a ticket and include the > logs? https://issues.apache.org/jira/browse/CASSANDRA > > On Mon, Jun 13,

Re: cqlsh problem

hi, Patric, [image: 内嵌图片 1], netstat -lepunt looks like above 2016-05-27 23:16 GMT+08:00 Patrick McFadin : > Can you do a netstat -lepunt and show the output? If Cassandra is running > you aren't trying to connect to the ip/port it's bound to. > > Patrick > > > On Monday, May