As stated in the docs, using the core admin API when using SolrCloud is not
recommended,
for just reasons like this. While SolrCloud _does_ use the Core Admin API, it’s
usage
has to be very precise.
You apparently didn’t heed this warning in the UNLOAD command for the
collections API:
"Unloading all cores in a SolrCloud collection causes the removal of that
collection’s metadata from ZooKeeper.”
This latter is what the “non legacy mode…” message is about. In earlier
versions of Solr,
the ZK information was recreated when Solr found a core.properties file, but
that had
its own problems so was removed.
Your best bet now is to wipe your directories, create a new collection and
re-index.
If you absolutely can’t reindex:
0> save away one index directory from every shard, it doesn’t matter which.
1> create the collection, with the exact same number of shards and a
replicationFactor of 1
2> shut down all the Solr instances
3> copy the index directory from <0> to ’the right place”. For instance, if you
have a collection blah, you’ll have some directory like
blah_shard1_replica_n1/data/index.
It’s critical that you replace the contents of data/index with the contents
of the
directory saved in <0> from the _same_ shard, shard1 in this example.
4> start your Solr instances back up
5> use ADDREPLICA to build out the collection to have as many replicas as you
need.
Good luck!
Erick
> On Nov 12, 2020, at 6:32 AM, Gajanan <[email protected]> wrote:
>
> I have unloaded all cores of a collection in SolrCloud (8.x.x ) using
> coreAdmin APIs as UNLOAD collection is not available in collections API. Now
> I want reload the unloaded collection using APIs only.
> When trying with coreAdmin APIs I am getting "Non legacy mode CoreNodeName
> not found."
> When trying with collections APIs it is reloaded but shows no cores
> available.
>
>
>
>
> --
> Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
