You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Yongkang Li (Jira)" <ji...@apache.org> on 2021/10/26 12:58:00 UTC
[jira] [Created] (CASSANDRA-17067) Upgrade failure caused by the
change of value of `num_token`
Yongkang Li created CASSANDRA-17067:
---------------------------------------
Summary: Upgrade failure caused by the change of value of `num_token`
Key: CASSANDRA-17067
URL: https://issues.apache.org/jira/browse/CASSANDRA-17067
Project: Cassandra
Issue Type: Bug
Reporter: Yongkang Li
After shutting down the node(3.11.10), I started the node with the newer version(4.0.0) software and the newer default configuration file (conf/cassandra.yaml) but came across a failure. After changing the value of `num_token` from 16 to 256 (the value in the default configuration file of 3.11.10) in the configuration file, the node can be started successfully with the 4.0.0 software. I wonder whether this should be clear in the corresponding document.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org