Hi DuyHai,
Thanks for the detailed response! A few responses below:
"On a side node, your usage of secondary index is not the best one. Indeed,
indexing the update date will lead to a situation where for one date,
you'll mostly have one or a few matching items (assuming that the update
date reso
Hi,
When you configured the new node, did you correctly configure your seeds
and listen address?
Mark
On Mon, Aug 11, 2014 at 6:12 PM, Rahul Gupta
wrote:
> I have a 3 node Cassandra cluster and I am adding a new node when I get
> below error during bootstrap.
>
> Running DataStax ver 4.5 (C
Thanks Mark, indeed changing port to 9042 worked.
In addition I set following parameters in my cassandra.yaml
rpc_address: 0.0.0.0
broadcast_rpc_address: 1.2.3.4 ( External IP address of my EC2 machine)
Regards,
-Subodh Nijsure
On Sun, Aug 10, 2014 at 6:13 AM, Mark Reddy wrote:
> Hi,
>
> Whil
I have a 3 node Cassandra cluster and I am adding a new node when I get below
error during bootstrap.
Running DataStax ver 4.5 (Cassandra 2.0.8.39) on all the nodes. Nodes are VMs
running on VMWare .
Any ideas what might be wrong here?
INFO [main] 2014-08-11 13:01:09,427 StorageService.java (li