dsetool unload_core with distributed=false command unloads core from all the nodes..is there any way I can unload only from local node or local DC not entire cluster.please let me know if more information required on this.
dsetool unload_core with distributed=false command unloads core from all the nodes..is there any way I can unload only from local node or local DC not entire cluster.please let me know if more information required on this.
@rakeshgouda1992_96602 Unloading a Solr core from just one node is not a valid operation in DSE Search since it is not possible to disable Solr operations on just one node. Unloading a core will always apply to all nodes in a Search DC so distributed=false
does not have any effect. Cheers!
Thanks for the clarification.
Is it possible to unload from a particular DC in a multi DC cluster.
EDIT: @rakeshgouda1992_96602 After some internal discussion, I'm revising my previous response and confirm that unloading a core will unload it from ALL Search DCs. It is not possible to unload it from just one particular DC.
As a side note, we will update the documentation to make this distinction clear. Cheers!
Correct,it should only unload from a specific DC,but in my case with 2 DC cluster with both search enabled,when I perform unload core on one specific DC it unloads from both the DC.
Is there any other way I can unload only from one DC.
Below are my observations after testing on a 2DC cluster DC1, DC2 having 5 nodes each.
Whene we unload_core on DC1, It deletes all the solr resources, solr directories and indexes from DC1 and it unloads only the core from DC2 , However the solr indexes and directories on DC2 remain as it is.
$ dsetool unload_core keyspace_name.table deleteDataDir=true deleteResources=true distributed=true
Once we create_core with modified schema and solrconfig file on DC1, DC2 will continue to use the previous index.
$ dsetool write_resource keyspace_name.table name=schema.xml file=./schema.xml $ dsetool write_resource keyspace_name.table name=solrconfig.xml file=./solrconfig.xml $ dsetool create_core keyspace_name.table reindex=true distributed=true
Once the reindexing is completed in DC1, run a reload_core command in DC2
FYI I've converted your post to a comment since it is not an "answer". Cheers!
6 People are following this question.
DataStax Enterprise is powered by the best distribution of Apache Cassandra ™
© 2023 DataStax, Titan, and TitanDB are registered trademarks of DataStax, Inc. and its subsidiaries in the United States and/or other countries.
Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.
Privacy Policy Terms of Use