Re: Error creating pool to /IP_ADDRESS33:9042 (Proving Cassandra's NO SINGLE point of failure)

2016-10-26 Thread Edward Capriolo
I would suggest you look some existing work http://techblog.netflix.com/2014/07/revisiting-1-million-writes-per-second.html and attempt to re-create those scenarios and methodologies for failing nodes and seeing the performance impact. This would yield faster and more easily verifiable results

RE: Error creating pool to /IP_ADDRESS33:9042 (Proving Cassandra's NO SINGLE point of failure)

2016-10-26 Thread Rajesh Radhakrishnan
Hi Vladimir, Thank you for the response. Yes I added all the three node IPs while connecting to the cluster via driver. Its not failed operation. while the script is running and it takes some time to read millions of data and during this time , I intentionally put one node down to see how the

Re: Error creating pool to /IP_ADDRESS33:9042 (Proving Cassandra's NO SINGLE point of failure)

2016-10-24 Thread Vladimir Yudovin
Probably used Python driver can't restart failed operation with connection to other node. Do you provide all three IPs to Python driver for connecting? Best regards, Vladimir Yudovin, Winguzone - Hosted Cloud Cassandra Launch your cluster in minutes. On Mon, 24 Oct 2016 07:48:05

Error creating pool to /IP_ADDRESS33:9042 (Proving Cassandra's NO SINGLE point of failure)

2016-10-24 Thread Rajesh Radhakrishnan
Hi, I have 3 nodes Cassandra cluster. Cassandra version : dsc-cassandra-2.1.5 Python Cassandra Driver : 2.5.1 Running the nodes in Red Hat virtual machines. Node ip info: Node 1: IP_ADDRESS219 Node 2: IP_ADDRESS229 Node 3: IP_ADDRESS230 (IP_ADDRESS219 is masked for this email which