C*/Nodejs REST API integration

Hi I am using REST API to insert data into C* using below reference link. http://docs.datastax.com/en/developer/nodejs-driver/2.0/nodejs-driver/quick_start/qsSimpleClientExecutingQueries.html However the insert performance is extremely lagging. *Can anyone has experience with Nodejs driver for

Re: Lots of write timeouts and missing data during decomission/bootstrap

WOW.. nice. you rock!! On Wed, Jul 1, 2015 at 3:18 PM, Robert Coli wrote: > On Wed, Jul 1, 2015 at 2:58 PM, Kevin Burton wrote: > >> Looks like all of this is happening because we’re using CAS operations >> and the driver is going to SERIAL consistency level. >> ... >> This is Cassandra 2.0.9 b

Re: Error while adding a new node.

also: root@cas03:~# sudo service cassandra start root@cas03:~# lsof -n | grep java | wc -l 5315 root@cas03:~# lsof -n | grep java | wc -l 977317 root@cas03:~# lsof -n | grep java | wc -l 880240 root@cas03:~# lsof -n | grep java | wc -l 882402 On Wed, Jul 1, 2015 at 6:31 PM, Neha Trivedi wrote:

Re: Truncate really slow

On Wed, Jul 1, 2015 at 2:58 PM, horschi wrote: > you have to enable -Dcassandra.unsafesystem=true in cassandra-env.sh. Also > disable durables writes for your CFs. > > This should speed things up and should reduce IOWait dramatically. > The above two suggestions are almost always bad advice anyw

Re: Lots of write timeouts and missing data during decomission/bootstrap

On Wed, Jul 1, 2015 at 2:58 PM, Kevin Burton wrote: > Looks like all of this is happening because we’re using CAS operations and > the driver is going to SERIAL consistency level. > ... > This is Cassandra 2.0.9 btw. > > https://issues.apache.org/jira/browse/CASSANDRA-8640 =Rob (credit to iamal

Re: Truncate really slow

Hi, you have to enable -Dcassandra.unsafesystem=true in cassandra-env.sh. Also disable durables writes for your CFs. This should speed things up and should reduce IOWait dramatically. kind regards, Christian On Wed, Jul 1, 2015 at 11:52 PM, Robert Wille wrote: > I have two test clusters, both

Re: Lots of write timeouts and missing data during decomission/bootstrap

Looks like all of this is happening because we’re using CAS operations and the driver is going to SERIAL consistency level. SERIAL and LOCAL_SERIAL write failure scenarios¶ > >

Truncate really slow

I have two test clusters, both 2.0.15. One has a single node and one has three nodes. Truncate on the three node cluster is really slow, but is quite fast on the single-node cluster. My test cases truncate tables before each test, and > 95% of the time in my test cases is spent truncating tables

Lots of write timeouts and missing data during decomission/bootstrap

We get lots of write timeouts when we decommission a node. About 80% of them are write timeout and just about 20% of them are read timeout. We’ve tried to adjust streamthroughput (and compaction throughput) for that matter and that doesn’t resolve the issue. We’ve increased write_request_timeout

Re: Cassandra leap second

Here is the full Datastax article: http://www.datastax.com/dev/blog/preparing-for-the-leap-second We had issues with C* and MySQL last time around (2012) but no issues this time thanks to upgraded systems. On 1 July 2015 at 14:39, Alain RODRIGUEZ wrote: > I think it is more a kernel / java vers

Re: Stream failure while adding a new node

David ; bring down all the nodes with the exception of the 'seed' node.Now bring up the 10th node.   Run 'nodetool status'  and wait until this 10th node is UP. Bring up the rest of the nodes after that. Run  'nodetool status'  again and check that all the nodes are UP.   Alternatively;decommiss

Re: Issue when node goes away?

On Wed, Jul 1, 2015 at 12:14 PM, Jonathan Haddad wrote: > Adding new nodes of a different version is asking for trouble, as others > have said. I don't know if this particular version bump would expect any > issues, but why risk it? If you want to upgrade, do it to the nodes in > place. Don't

Re: Issue when node goes away?

I understand - I was actually trying to use the containerized Cassandra, so upgrading in place doesn't make sense. I guess I'll wait until that's better supported. On Wed, Jul 1, 2015 at 12:14 PM, Jonathan Haddad wrote: > Adding new nodes of a different version is asking for trouble, as others

Re: How to measure disk space used by a keyspace?

nodetool cfstats would be your best bet.   Sum all the column families info.,  within a keyspace to get to the number you are looking for.  Jan/ On Wednesday, July 1, 2015 9:05 AM, graham sanderson wrote: If you are pushing metric data to graphite, there is org.apache.cassandra.met

Re: Issue when node goes away?

Adding new nodes of a different version is asking for trouble, as others have said. I don't know if this particular version bump would expect any issues, but why risk it? If you want to upgrade, do it to the nodes in place. Don't bootstrap new nodes, don't run repair, don't remove nodes. My 2 ce

Re: Issue when node goes away?

I mean add an additional two nodes to my cluster and pointing them at the other nodes in the cluster, to handle data migration. On Wed, Jul 1, 2015 at 11:40 AM, Jonathan Haddad wrote: > When you say add 2 nodes, do you mean bootstrap, or upgrade in place? > > On Wed, Jul 1, 2015 at 11:37 AM Davi

Re: Issue when node goes away?

This helps - so let me understand: Starting point: - 4 nodes running 2.1.4 - System is healthy Decide to upgrade: - Add 2 nodes running 2.1.5 - Run nodetool upgradestable - Wait until system is healthy - Stop 2 nodes running 2.1.4 - Run nodetool upgradestable - Add 2 nodes running 2.1.5

Re: Issue when node goes away?

When you say add 2 nodes, do you mean bootstrap, or upgrade in place? On Wed, Jul 1, 2015 at 11:37 AM David Aronchick wrote: > This helps - so let me understand: > > Starting point: > - 4 nodes running 2.1.4 > - System is healthy > > Decide to upgrade: > - Add 2 nodes running 2.1.5 > - Run n

Re: High load on cassandra node

We heavily use counters, will upgrade and check if it solves the issue... The current cluster version is 2.0.14 We do a lot of delete operations and do major compaction to remove the tombstones. Is there any better way? On 1 July 2015 at 20:02, Sebastian Estevez wrote: > Looks like a CASSANDRA-6

Experiencing Timeouts on one node

We have a 28 node cluster, out of which only one node is experiencing timeouts. We thought it was the raid, but there are two other nodes on the same raid without any problem. Also The problem goes away if we reboot the node, and then reappears after seven days. The following hinted hand-off timeo

Re: How to measure disk space used by a keyspace?

If you are pushing metric data to graphite, there is org.apache.cassandra.metrics.keyspace..LiveDiskSpaceUsed.value … for each node; Easy enough to graph the sum across machines. Metrics/JMX are tied together in C*, so there is an equivalent value exposed via JMX… I don’t know what it is called

Re: Migrate table data to another table

Not yet, there is a ticket for CTAS for copy which will use spark to do what you are looking for. On Jul 1, 2015 3:31 AM, "Umut Kocasaraç" wrote: > In both methods i have to export table to one file and the i can move data > to new table. Can i copy from one table to another? > > 30 Haz 2015 Sal

Re: Cassandra leap second

I think it is more a kernel / java version issue than a Cassandra version related issue. >From Datastax: "Leap Second on June 30, 2015 Required Actions: Ensure that you are running on kernel version 3.4 or higher and using JDK version 7u60 or higher. This should protect you from the livelock pr

RE: Stream failure while adding a new node

Hi Alain, We still have the timeout problem in OPSCenter and we still didn’t solve this problem so no we didn’t ran an entire repair with the repair service. And yes, during this try, we’ve set auto_bootstrap to true and ran a repair on the 9th node after it finished streaming. Thank you for yo

Re: High load on cassandra node

Looks like a CASSANDRA-6405 (replicate on write is the counter tp). Upgrade to the latest 2.1 version and let us know if he situation improves. Major compactions are usually a bad idea by the way. Do you really want one huge sstable? On Jul 1, 2015 10:03 AM, "Jayapandian Ponraj" wrote: > HI I ha

Re: Cassandra leap second

We also experienced same, i.e. high cpu on Cassandra 1.1.4 node running in AWS. Restarting the vm worked. On Wed, Jul 1, 2015 at 4:58 AM, Jason Wee wrote: > same here too, on branch 1.1 and have not seen any high cpu usage. > > On Wed, Jul 1, 2015 at 2:52 PM, John Wong wrote: > >> Which version

RE: How to measure disk space used by a keyspace?

That’s ok for a single node, but to answer the question, “how big is my table across the cluster?” it would be much better if the cluster could provide an answer. Sean Durity From: Jonathan Haddad [mailto:j...@jonhaddad.com] Sent: Monday, June 29, 2015 8:15 AM To: user Subject: Re: How to measu

High load on cassandra node

HI I have a 6 node cluster and I ran a major compaction on node 1 but I found that the load reached very high levels on node 2. Is this explainable? Attaching tpstats and metrics: cassandra-2 ~]$ nodetool tpstats Pool NameActive Pending Completed Blocked All time blo

Re: Error while adding a new node.

One of the column family has SStable count as under : SSTable count: 98506 Can it be because of 2.1.3 version of cassandra.. I found this : https://issues.apache.org/jira/browse/CASSANDRA-8964 regards Neha On Wed, Jul 1, 2015 at 5:40 PM, Jason Wee wrote: > nodetool cfstats? > > On Wed, Jul 1,

Re: Error while adding a new node.

nodetool cfstats? On Wed, Jul 1, 2015 at 8:08 PM, Neha Trivedi wrote: > Hey.. > nodetool compactionstats > pending tasks: 0 > > no pending tasks. > > Dont have opscenter. how do I monitor sstables? > > > On Wed, Jul 1, 2015 at 4:28 PM, Alain RODRIGUEZ > wrote: > >> You also might want to check

Re: Error while adding a new node.

Hey.. nodetool compactionstats pending tasks: 0 no pending tasks. Dont have opscenter. how do I monitor sstables? On Wed, Jul 1, 2015 at 4:28 PM, Alain RODRIGUEZ wrote: > You also might want to check if you have compactions pending (Opscenter / > nodetool compactionstats). > > Also you can mo

Re: Cassandra leap second

same here too, on branch 1.1 and have not seen any high cpu usage. On Wed, Jul 1, 2015 at 2:52 PM, John Wong wrote: > Which version are you running and what's your kernel version? We are still > running on 1.2 branch but we have not seen any high cpu usage yet... > > On Tue, Jun 30, 2015 at 11:1

Re: Error while adding a new node.

You also might want to check if you have compactions pending (Opscenter / nodetool compactionstats). Also you can monitor the number of sstables. C*heers Alain 2015-07-01 11:53 GMT+02:00 Neha Trivedi : > Thanks I will checkout. > I increased the ulimit to 10, but I am getting the same erro

Seed gossip version error

Hi, I have a running cluster running with version 2.1.7. Two of the machines went down and they are not joining the cluster even after restart. I see the following WARN message in system.log in all the nodes: system.log:WARN [MessagingService-Outgoing-cassandra2.cleartrip.com/172.18.3.32] 2015

Re: Error while adding a new node.

Thanks I will checkout. I increased the ulimit to 10, but I am getting the same error, but after a while. regards Neha On Wed, Jul 1, 2015 at 2:22 PM, Alain RODRIGUEZ wrote: > Just check the process owner to be sure (top, htop, ps, ...) > > > http://docs.datastax.com/en/cassandra/2.0/cassan

Re: Error while adding a new node.

Just check the process owner to be sure (top, htop, ps, ...) http://docs.datastax.com/en/cassandra/2.0/cassandra/install/installRecommendSettings.html#reference_ds_sxl_gf3_2k__user-resource-limits C*heers, Alain 2015-07-01 7:33 GMT+02:00 Neha Trivedi : > Arun, > I am logging on to Server as ro

Re: Issue when node goes away?

Basically, when you add nodes, add them on the correct version to avoid schema / network issues in your streams. Also, try to update all the node using rolling restarts in a reduced time frame after stopping repairs, with all the nodes up, etc. You must have a healthy cluster before performing an

Re: Decommissioned node still in Gossip

Hi, just a guess, there was a possibility to purge gossip state on a node, at least in version 1.2 http://docs.datastax.com/en/cassandra/1.2/cassandra/architecture/architectureGossipPurge_t.html the trick was to add -Dcassandra.load_ring_state=false somehow to the jvm parameters I'm not sure if

Re: Migrate table data to another table

In both methods i have to export table to one file and the i can move data to new table. Can i copy from one table to another? 30 Haz 2015 Sal, 20:31 tarihinde, Sebastian Estevez < sebastian.este...@datastax.com> şunu yazdı: > Another option is Brian's cassandra loader: > > https://github.com/bri

Re: Decommissioned node still in Gossip

Thanks for the tip Aiman, but this node is not in the seed list anywhere. Jeff On 30 June 2015 at 18:16, Aiman Parvaiz wrote: > I was having exactly the same issue with the same version, check your seed > list and make sure it contains only the live nodes, I know that seeds are > only read when