[
https://issues.apache.org/jira/browse/CASSANDRA-14201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358850#comment-16358850
]
Ariel Weisberg commented on CASSANDRA-14201:
--------------------------------------------
For MBeans do we really modify the MBean in place or add a new method and
deprecate the old one? We don't want to break tooling on upgrade most of the
time right since people will do rolling upgrades. This also means you can
preserve the existing behavior and verifications in the old signature if that
is a good idea. Maybe we want to protect people from what were really bad
defaults in the old version. Still seems like we should keep the signature
around so we don't break automation.
Otherwise +1 once we have an answer for the appropriate handling of the MBean
interface.
> Add a few options to nodetool verify
> ------------------------------------
>
> Key: CASSANDRA-14201
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14201
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Major
> Fix For: 4.x
>
>
> {{nodetool verify}} currently invokes the disk failure policy when it finds a
> corrupt sstable - we should add an option to avoid that. It should also have
> an option to check if all sstables are the latest version to be able to run
> {{nodetool verify}} as a pre-upgrade check
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
