[
https://issues.apache.org/jira/browse/CASSANDRA-17067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434386#comment-17434386
]
Brandon Williams edited comment on CASSANDRA-17067 at 10/26/21, 3:45 PM:
-------------------------------------------------------------------------
Which document are you referring you?
Generally for major upgrades you should read through NEWS.txt and manually
migrate your yaml to merge any existing changes and new features.
This is expected behavior from CASSANDRA-13701.
was (Author: brandon.williams):
Which document are you referring you?
Generally for major upgrades you should read through NEWS.txt and manually
migrate your yaml to merge any existing changes and new features.
> 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]
