[
https://issues.apache.org/jira/browse/CASSANDRA-19151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18081493#comment-18081493
]
Dmitry Konstantinov commented on CASSANDRA-19151:
-------------------------------------------------
[~samt] [~n.v.harikrishna] it looks like the patch has changed a name for
addtocmstool script which is mentioned in OS packages building logic:
[https://github.com/search?q=repo%3Aapache%2Fcassandra%20addtocmstool&type=code]
so, it starts to fail:
{code:java}
dh_install: warning: Cannot find (any matches for) "tools/bin/addtocmstool"
(tried in ., debian/tmp) dh_install: warning: cassandra-tools missing files:
tools/bin/addtocmstooldh_install: error: missing files, abortingmake: ***
[debian/rules:54: install] Error 25dpkg-buildpackage: error: fakeroot
debian/rules binary subprocess returned exit status 2 {code}
https://ci-cassandra.apache.org/view/Cassandra%206.0/job/Cassandra-6.0/25/cloudbees-pipeline-explorer/?filter=6269
> Add an offline cluster metadata tool for disaster recovery scenarios
> --------------------------------------------------------------------
>
> Key: CASSANDRA-19151
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19151
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Transactional Cluster Metadata
> Reporter: Alex Petrov
> Assignee: n.v.harikrishna
> Priority: Normal
> Fix For: 6.0-alpha2
>
> Attachments: ci_summary-1.html, result_details.tar.gz
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> We currently have an offline tool to make a node CMS
> We should add a tool (or update the existing one) to
> * completely forget a node id
> * add an instance at a given token
> * force move a nodeid to JOINED
> * dump the cluster metadata in a human readable format
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
