I agreed Michael. I was generating stuff for it again, Looks like they had
the SSL stack changed. I came from 2.1.6 to 2.2.0. Thanks.
On Wed, Jul 22, 2015 at 5:45 PM, Michael Shuler
wrote:
> What version of Cassandra did you upgrade to 2.2.0 *from*?
>
> This would help with looking at config dif
What version of Cassandra did you upgrade to 2.2.0 *from*?
This would help with looking at config differences, changelogs, etc.
It seems you have some pretty clear SSL connection errors, according to
the logs, which at least helps with seeing why the nodes can't talk to
each other. I'm not ter
Thanks for the reply, Michael!
Yes, I did followed the upgrade nodes.
I am running Ubuntu Ubuntu 14.04.2 LTS on all and kernel 3.13.0-57-generic
on all.
I have 4 machines: .31, .32, .33 and .34. If I run nodetool status from .34
I now see all the others as DN the same happens if I log in from th
On 07/22/2015 04:45 PM, Carlos Scheidecker wrote:
I have a 4 node Cassandra system running on 4 Ubuntu boxes. After
updating to Cassandra 2.2.0 and keeping the same cassandra.yaml file,
the nodes cannot see each other.
What version did you upgrade from?
Usually, when upgrading, it is probably
All,
I have a 4 node Cassandra system running on 4 Ubuntu boxes. After updating
to Cassandra 2.2.0 and keeping the same cassandra.yaml file, the nodes
cannot see each other.
When I do a nodetool status it only reports as being up the machine where I
had issue the command.
In other words, all the
All,
I have a 4 node Cassandra system running on 4 Ubuntu boxes. After updating
to Cassandra 2.2.0 and keeping the same cassandra.yaml file, the nodes
cannot see each other.
When I do a nodetool status it only reports as being up the machine where I
had issue the command.
In other words, all the
