[
https://issues.apache.org/jira/browse/CASSANDRA-13954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16206584#comment-16206584
]
Aleksey Yeschenko commented on CASSANDRA-13954:
-----------------------------------------------
Branches for [3.0|https://github.com/iamaleksey/cassandra/commits/13954-3.0],
[3.11|https://github.com/iamaleksey/cassandra/commits/13954-3.11],
[4.0|https://github.com/iamaleksey/cassandra/commits/13954-4.0]. Dtest
[here|https://github.com/iamaleksey/cassandra-dtest/commits/13954].
CircleCI for [3.0|https://circleci.com/gh/iamaleksey/cassandra/60],
[3.11|https://circleci.com/gh/iamaleksey/cassandra/58],
[4.0|https://circleci.com/gh/iamaleksey/cassandra/59].
Dtest run just for
[3.0|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/375/].
> Provide a JMX call to sync schema with local storage
> ----------------------------------------------------
>
> Key: CASSANDRA-13954
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13954
> Project: Cassandra
> Issue Type: New Feature
> Components: Distributed Metadata
> Reporter: Aleksey Yeschenko
> Assignee: Aleksey Yeschenko
> Priority: Minor
> Fix For: 3.0.x, 3.11.x
>
>
> As discussed in CASSANDRA-13813 comments, we need such a call / nodetool
> command to enable the workaround for CASSANDRA-12701.
> This is technically a new feature and shouldn't go into 3.0.x, however in
> practical terms it's part of a solution to CASSANDRA-12701, which is a bug,
> and an pre-requisite for CASSANDRA-13813 - which is also a bug.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
