DataStax Cassandra MVP 2015 roster

So glad to be one of the awarded and big congratulations to everyone else in that list!! http://www.planetcassandra.org/mvps/ Thanks DataStax and let's keep pushing this product/community for more!! Carlos Alonso | Software Engineer | @calonso

Cassandra users survey

With 3.0 approaching, the Apache Cassandra team would appreciate your feedback as we work on the project roadmap for future releases. I've put together a brief survey here: https://docs.google.com/forms/d/1TEG0umQAmiH3RXjNYdzNrKoBCl1x7zurMroMzAFeG2Y/viewform?usp=send_form Please take a few

Re: Currupt sstables when upgrading from 2.1.8 to 2.1.9

On Wed, Sep 30, 2015 at 3:08 AM, George Sigletos wrote: > This is way too many manual steps. I was wondering why not just removing > the entire /var/lib/cassandra/data folder + commitlogs, restart the node > again and wait to catch up > Briefly, there is a low but

Re: Question about addition of node in a DC while a node is down in another DC

On Wed, Sep 30, 2015 at 8:12 AM, K F wrote: > I had a question where I have my cassandra cluster running in vnodes. And > we would like to add some nodes in DC1 while there is a node down in DC2. > So, my question to you all is it ok to add nodes to DC1 while there is a >

Re: Cassandra shutdown during large number of compactions - now fails to start with OOM Exception

On Mon, Sep 21, 2015 at 4:09 AM, Walsh, Stephen wrote: > Although I didn’t get an answer on this, it’s worth noting the removing > the compaction_in_progress folder resolved the issue. > This stuff is being re-written upstream, FWIW.

Re: Consistency Issues

On Wed, Sep 30, 2015 at 9:06 AM, Walsh, Stephen wrote: > > We never had these issue with our first run. Its only when we added > another 25% of writes. > As Jack said, you are probably pushing your GC over a threshold, leading to long pause times and inability to meet

Re: Currupt sstables when upgrading from 2.1.8 to 2.1.9

Hello again and sorry for the late response, Still having problems with upgrading from 2.1.8 to 2.1.9. I decided to start the problematic nodes with "disk_failure_policy: best_effort" Currently running "nodetool scrub " Then removing the corrupted sstables and planning to run repair

broadcast address on EC2 without Elastic IPs.

Hello! I have configured a small cluster composed of three nodes on Amazon EC2. The 3 machines don't have an elastic IP (static address) so the public address changes at every reboot. I have a machine with a static ip that I use as a bridge to access the other 3 cassandra nodes through SSH. On

Consistency Issues

Hi there, We are having some issues with consistency. I'll try my best to explain. We have an application that was able to Write ~1000 p/s Read ~300 p/s Total CF created: 400 Total Keyspaces created : 80 On a 4 node Cassandra Cluster with Version 2.1.6 Replication : 3 Consistency (Read &

Re: Consistency Issues

Can you provide exact details on where your load balancer is? Like Michael said, you shouldn't need one between your client and the c* cluster if you're using a DataStax driver. All the best, [image: datastax_logo.png] Sebastián Estévez Solutions Architect | 954 905

RE: Consistency Issues

Many thanks for your reply Sebastian, But the load balancer is being used with our applications, not with Cassandra. It just allows use to increase the through-put to Cassandra Our Generation Tool -> Load Balancer -> Our Processing Application -> Cassandra Sebastian, is jack correct in best

Re: broadcast address on EC2 without Elastic IPs.

You may get a better/faster response by asking directly on the java driver list: https://groups.google.com/a/lists.datastax.com/forum/#!forum/java-driver-user 2015-09-30 10:24 GMT-04:00 Renato Perini : > Hello! > I have configured a small cluster composed of three nodes

Question about addition of node in a DC while a node is down in another DC

Hi Cassandra users, I had a question where I have my cassandra cluster running in vnodes. And we would like to add some nodes in DC1 while there is a node down in DC2. So, my question to you all is it ok to add nodes to DC1 while there is a node down in DC2? Thanks for the response.

RE: Consistency Issues

Many thanks all, The Load balancers are only between our own node and not as a middle-man to Cassandra. It’s just so we can push more data into Cassandra. The only reason we are not using 2.1.9 is time , we haven’t had time to test upgrades. I wasn’t able to find any best practices for number

Re: Consistency Issues

More than "low hundreds" (200 or 300 max, and preferably under 100) of tables/column families is not exactly a recommended best practice. You may be able to get it to work, but probably only with very heavy tuning (i.e., lots of time and playing with options) on your own part. IOW, no quick and

RE: Consistency Issues

More information, I've just setup a NTP server to rule out any timing issues. And I also see this in the Cassandra node log files MessagingService-Incoming-/172.31.22.4] 2015-09-30 15:19:14,769 IncomingTcpConnection.java:97 - UnknownColumnFamilyException reading from socket; closing

Re: Consistency Issues

What client are you using? Official java and python clients should not have a LB between them and the C* nodes AFAIK. Why aren't you using 2.1.9? Have you checked for schema agreement amongst all nodes? ml On Wed, Sep 30, 2015 at 11:22 AM, Walsh, Stephen wrote: >