cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rajesh Radhakrishnan <>
Subject Error creating pool to /IP_ADDRESS33:9042 (Proving Cassandra's NO SINGLE point of failure)
Date Mon, 24 Oct 2016 11:48:05 GMT

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 represents something similar 123.321.123.219)

Cassandra.yaml configuration details of node1:

listen_address: IP_ADDRESS219
broadcast_address: commented
rpc_address: IP_ADDRESS219
broadcast_rpc_address : commented

The IP address of the node is ( using the ifconfig command ) IP_ADDRESS219.

While the cluster is up and running , when I put Node 3 (IP_ADDRESS230) down, I was able to
connect to CQLSH from IP_ADDRESS219 and IP_ADDRESS229.

But while I was running a Python script which just reads data from Cassandra using the cassandra-python-driver,
and when the Node 3 stops(while the script is still running I intentionally stops  node3).

Then the script comes to a halt with OperationTimedOut: errors={}, last_host= IP_ADDRESS219.

However if I run the script when node3 is already down, it runs and reads data.

So during the reading operation  if any of the nodes in the cluster goes down its affects
the client operation??? Does anyone has similar situation.

Here we are trying to establish or prove Cassandra's always on (NO single point of failure).
 Do you know why this is happening Thank you .

Kind regards,
Rajesh R

The information contained in the EMail and any attachments is confidential and intended solely
and for the attention and use of the named addressee(s). It may not be disclosed to any other
person without the express authority of Public Health England, or the intended recipient,
or both. If you are not the intended recipient, you must not disclose, copy, distribute or
retain this message or any part of it. This footnote also confirms that this EMail has been
swept for computer viruses by Symantec.Cloud, but please re-sweep any attachments before opening
or saving.
View raw message