Thanks for the replies. Wanted to make sure that I am not missing on
something already available. Now that everything is clear, I may have to go
for application re-design or choose an approach, not so elegant, as
suggested.
Thanks all.
-Gajanan
--
Sent from: https://lucene.472066.n3.nabble.com/
An unelegant alternative is to back up and delete a collection in lieu of
unload, restore it in lieu of load...
Ilan
On Sun, Nov 15, 2020 at 6:56 PM Erick Erickson
wrote:
> I don’t really have any good alternatives. There’s an open JIRA for
> this, see: SOLR-6399
>
> This would be a pretty big
I don’t really have any good alternatives. There’s an open JIRA for
this, see: SOLR-6399
This would be a pretty big chunk of work, which is one of the reasons
this JIRA has languished…
Sorry I can’t be more helpful,
Erick
> On Nov 15, 2020, at 11:00 AM, Gajanan wrote:
>
> Hi Erick, thanks for
Hi Erick, thanks for the reply.
I am working on a application where a solr collection is being created per
usage of application accumulating lot of them over period of time . In order
to keep memory requirements under control, I am unloading collections not in
current usage and loading them whenev
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:
"Unload
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 try
