Hi Aaron,
Thank you for your support. It was my mistake indeed. The second node was
still configured to have the internode comm to be compressed.
After I fixed it, I'm able to start my cluster.
Cheers
On Thu, Apr 11, 2013 at 12:40 PM, aaron morton wrote:
> I've already tried to set internode
> I've already tried to set internode_compression: none in my yaml files.
What version are you on?
If you've set internode_compression to none and restarted? Can you double check.
The code stack shows cassandra deciding that the connection should be
compressed.
Cheers
-
Aaron
Hi,
I'm trying to set up a cassandra cluster for some experiments on my
raspberry pies but I'm still having trouble to join my nodes to the cluster.
I started with two nodes (192.168.2.3 and 192.168.2.7) and when I start the
cassandra, I see the following exception on the node 192.168.2.7
ERROR [