[
https://issues.apache.org/jira/browse/CASSANDRA-15192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
C. Scott Andreas updated CASSANDRA-15192:
-----------------------------------------
Resolution: Information Provided
Status: Resolved (was: Triage Needed)
This JIRA is used for the development and bug tracking of the Apache Cassandra
project itself.
The best avenue for asking questions about operational / support issues is via
the user community mailing list or ASF Slack. Here's a link with more
information: http://cassandra.apache.org/community/
> Why a added new node stop an old node to start?
> -----------------------------------------------
>
> Key: CASSANDRA-15192
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15192
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Membership
> Reporter: gloCalHelp.com
> Priority: Normal
> Attachments: StrangeNoErrorStopLogs.zip
>
>
> I have a running 3 datanodes with cassandra3.11.3 with a keyspace having a
> table over 10millions row in Centos6.9, after I added a node in win10 with
> cassandra3.11.4 for a whole night, this afternoon, one of the old 3 nodes can
> not start, and I use "nodetool decommission" on the new node and "nodetool
> removenode (new node's uuid)", but one of the 3 old node can not start with
> an no error system.log and debug.log as the attachment.
> Finally, I setting the failing old node's start JVM_OPTS to have
> {{-Dcassandra.reset_bootstrap_progress=true and it become
> live.[^StrangeNoErrorStopLogs.zip]}}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
