[
https://issues.apache.org/jira/browse/CASSANDRA-17067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-17067:
-----------------------------------------
Resolution: Not A Problem
Status: Resolved (was: Triage Needed)
> 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
> Priority: Normal
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
