Hi Jai,
As you suggested, I stopped my first node and restart now again. Now
updates are like this.
> On Node1:-
> WARN message is not coming.
> On Node 2:-
> WARN: CassandraRoleManager Skipped
> WARN: 10.0.0.3 node seems to be down
> On Node 3:-
> No Such Warning,
On Fri, Nov 24, 2017 at
yes,
I had it in one of my cluster. try restarting the node once again and see
if it creates the default role.
On Thu, Nov 23, 2017 at 5:05 PM, @Nandan@
wrote:
> So It means you are also getting same WARN into your output.log file.
> I am also getting this WARN
So It means you are also getting same WARN into your output.log file.
I am also getting this WARN into my NODE1.
On Fri, Nov 24, 2017 at 7:03 AM, Jai Bheemsen Rao Dhanwada <
jaibheem...@gmail.com> wrote:
> I ran into similar issue before with 2.1.13 version of C*. and when I
> restart the node
I ran into similar issue before with 2.1.13 version of C*. and when I
restart the node second time it actually created the default roles. I
haven't dig deeper on the root cause. it happened to me only on one cluster
out of 10+ clusters.
On Wed, Nov 22, 2017 at 5:13 PM, @Nandan@
Hi Jai,
I checked nodetool describecluster and got same schema version on all 4
nodes.
> [nandan@node-1 ~]$ nodetool describecluster
Cluster Information:
Name: Nandan
Snitch: org.apache.cassandra.locator.DynamicEndpointSnitch
Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
Schema
Can you do a nodetool describecluster and check if the schema version is
matching on all the nodes?
On Tue, Nov 21, 2017 at 11:52 PM, @Nandan@
wrote:
> Hi Team,
>
> Today I set up a test cluster with 4 nodes and using Apache Cassandra
> 3.1.1 version.
> After
Hi Team,
Today I set up a test cluster with 4 nodes and using Apache Cassandra 3.1.1
version.
After setup when I checked output.log file then I got WARN message as below
:-
WARN 08:51:38,122 CassandraRoleManager.java:355 - CassandraRoleManager
skipped default role setup: some nodes were not