[
https://issues.apache.org/jira/browse/CASSANDRA-21595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18124771#comment-18124771
]
Erick Ramirez edited comment on CASSANDRA-21595 at 10/7/26 11:48 PM:
---------------------------------------------------------------------
h2. Pre-merge verification
|| Branch || PR ||
| {{trunk}} | [#5225|https://github.com/apache/cassandra/pull/5225] |
| {{cassandra-6.0}} | [#5224|https://github.com/apache/cassandra/pull/5224] |
| {{cassandra-5.0}} | [#5047|https://github.com/apache/cassandra/pull/5047] |
For posterity, this is the current state of the Topology Changes page on the
website for
[5.0|https://cassandra.apache.org/doc/5.0/cassandra/managing/operating/topo_changes.html],
[6.0|https://cassandra.apache.org/doc/6.0/cassandra/managing/operating/topo_changes.html]
and
[{{trunk}}|https://cassandra.apache.org/doc/7.0/cassandra/managing/operating/topo_changes.html]:
!website-topo_changes-21595-pre.jpg|width=50%!
I've staged the website changes locally and the updates render as advertised
(note the single screenshot for all branches since they are identical):
!website-topo_changes-21595-post.jpg|width=50%!
was (Author: JIRAUSER285101):
h2. Pre-merge verification
|| Branch || PR ||
| {trunk} | [#5225|https://github.com/apache/cassandra/pull/5225] |
| {{cassandra-6.0}} | [#5224|https://github.com/apache/cassandra/pull/5224] |
| {{cassandra-5.0}} | [#5047|https://github.com/apache/cassandra/pull/5047] |
For posterity, this is the current state of the Topology Changes page on the
website for
[5.0|https://cassandra.apache.org/doc/5.0/cassandra/managing/operating/topo_changes.html],
[6.0|https://cassandra.apache.org/doc/6.0/cassandra/managing/operating/topo_changes.html]
and
[{{trunk}}|https://cassandra.apache.org/doc/7.0/cassandra/managing/operating/topo_changes.html]:
!website-topo_changes-21595-pre.jpg|width=50%!
I've staged the website changes locally and the updates render as advertised
(note the single screenshot for all branches since they are identical):
!website-topo_changes-21595-post.jpg|width=50%!
> docs: distinguish between reset_bootstrap_progress (true, false, unset)
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-21595
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21595
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Consistency/Bootstrap and Decommission, Documentation
> Reporter: Alexandre Viau
> Assignee: Alexandre Viau
> Priority: Normal
> Labels: patch-available
> Fix For: 5.0.x, 6.0.x, 7.0
>
> Attachments: Screenshot 2026-10-07 at 9.57.36 AM.png,
> website-topo_changes-21595-post.jpg, website-topo_changes-21595-pre.jpg
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> The only documenation available on `reset_bootstrap_progress` is the
> following:
> > In order to cleanup bootstrap state and start fresh, you may set the JVM
> > startup flag -Dcassandra.reset_bootstrap_progress=true.
> This gives the impression that if I don't want to start fresh, I should not
> do anything. However, this is false. If I want my node to resume bootstraping
> with existing data, I need to set it to `false`, which is different than the
> default of `unset`.
> I think this is impossible to infer from existing documentation. Only reading
> source code helped me understand.
>
> I opened a Merge Request on github here:
> https://github.com/apache/cassandra/pull/5047
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
