test mail please ignore

Re: Adding New Nodes/Data Center to an existing Cluster.

Sachin, Hope you are not using Cassandra 2.2 in production? regards Neha On Tue, Sep 1, 2015 at 11:20 PM, Sebastian Estevez < sebastian.este...@datastax.com> wrote: > DSE 4.7 ships with Cassandra 2.1 for stability. > > All the best, > > > [image: datastax_logo.png] > >

Amounts of ??CLOSE_WAIT?? status connection occur at cassandra servers

Hi, I encountered an issue recently when I built spark-cassandra applications envirenment. Problem description: 1. I run spark applications to process data then write result to cassandra. 2. In the beginning, all going well. But several hours(or serval days) later amounts of ??CLOSE_WAIT?

Point upgrades

I am wondering if when doing a point upgrade, such as 2.0.11 to 2.0.16 do I need to stop all repairs before performing an upgrade on node IF that node is NOT the one running the repair? Basically I would like to upgrade the other nodes, and then when the repair is done I can upgrade that node. Tha

Re: Network / GC / Latency spike

Hi Alain, Maybe it's possible to confirm this by testing on a small cluster: - create a cluster of 2 nodes (using https://github.com/pcmanus/ccm for example) - create a fake wide row of a few mb (using the python driver for example) - drain and stop one of the two nodes - remove the sstables of th

Re: Adding New Nodes/Data Center to an existing Cluster.

DSE 4.7 ships with Cassandra 2.1 for stability. All the best, [image: datastax_logo.png] Sebastián Estévez Solutions Architect | 954 905 8615 | sebastian.este...@datastax.com [image: linkedin.png] [image: facebook.png]

Free webinar on Times series IoT data ingestion into Cassandra using Kaa

[image: Time series IoT data ingestion into Cassandra using Kaa] We are glad to announce that a new webinar on using Kaa with Cass

Re: Adding New Nodes/Data Center to an existing Cluster.

@Neha, We are using DSE 4.7 & Cassandra 2.2 @Alain, I will check with out OPS team about repair vs rebuild and get back to you. Regards Sachin On Tue, Sep 1, 2015 at 5:59 AM, Alain RODRIGUEZ wrote: > Hi Sachin, > > You are speaking about a repair, when the proper command to do this is > "rebuil

[RELEASE] Apache Cassandra 2.2.1 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 2.2.1. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source an

Re: abnormal log after remove a node

Hi, I finally did the exact same thing before receiving the answer. I guess this will remain FTR :). Thanks though ! Alain 2015-09-01 16:22 GMT+02:00 曹志富 : > Just restart all of the c* node > > -- > Ranger Tsao > > 2015-08-25 18:17 GMT+08:00 Alain RODRIGUE

Re: abnormal log after remove a node

Just restart all of the c* node -- Ranger Tsao 2015-08-25 18:17 GMT+08:00 Alain RODRIGUEZ : > Hi, I am facing the same issue on 2.0.16. > > Did you solve this ? How ? > > I plan to try a rolling restart and see if gossip state recover from this. > > C*heers, >

Re: Re : Decommissioned node appears in logs, and is sometimes marked as "UNREACHEABLE" in `nodetool describecluster`

Are they in the system.peers table? On Aug 28, 2015 4:21 PM, "sai krishnam raju potturi" wrote: > We are using DSE on our clusters. > > DSE version : 4.6.7 > Cassandra version : 2.0.14 > > thanks > Sai Potturi > > > > On Fri, Aug 28, 2015 at 3:40 PM, Robert Coli wrote: > >> On Fri, Aug 28, 2015

Re: Upgrade from 2.1.0 to 2.1.9

Hi Tony. Did you read doc on Datastax site --> http://docs.datastax.com/en/upgrade/doc/upgrade/cassandra/upgradeCassandraDetails.html ? This being a minor upgrade I guess clients should not break, but it is often advised to test things, just in case, even more if you never did any update. I hear

Re: Adding New Nodes/Data Center to an existing Cluster.

Hi Sachin, You are speaking about a repair, when the proper command to do this is "rebuild" ? Did you tried adding your DC this way: http://docs.datastax.com/en/cassandra/2.1/cassandra/operations/ops_add_dc_to_cluster_t.html ? 2015-09-01 5:32 GMT+02:00 Neha Trivedi : > Hi, > Can you specify w

Re: Data Size on each node

Hi, Our migration to SSD (from m1.xl to I2.2xl on AWS) has been a big win. I mean we wen from 80 / 90 % disk utilisation to 20 % max. Basically, bottleneck are not disks performances anymore in our case. We get rid of one of our major issue that was disk contention. I highly recommend you to go a

Re: Network / GC / Latency spike

Hi Fabien, thanks for your help. I did not mention it but I indeed saw a correlation between latency and read repairs spikes. Though this is like going from 5 RR per second to 10 per sec cluster wide according to opscenter: http://img42.com/L6gx1 I have indeed some wide rows and this explanation

Re: Rebuild new DC nodes against new DC?

Hi Bryan, I have no clear answer to you yet I can give you some insights, my understanding of this. First, I am not sure that nodetool will let you "rebuild" from the DC the node is in. Then this would only work properly (if it works) because you have 3 nodes and a RF of 2 or 3 and so all the dat

Data Size on each node

We currently have a Cassandra Cluster spread over 2 DC. The data size on each node of the cluster is 1.2TB with spinning disk. Minor and Major compactions are slowing down our Read queries. It has been suggested that replacing Spinning disks with SSD might help. Has anybody done something similar?