gt;> that needs that core will cause it to be loaded (or reloaded).
>>>>
>>>> The admin/core/UNLOAD command, on the other hand, is designed to
>>>> _permanently_ remove the core from Solr. Or at least have it become
>>>> unavailable until another
then a
request directed to it would return an error instead.
Best,
Erick
On Wed, Oct 22, 2014 at 12:11 PM, Xiaolu Zhao
wrote:
Hi All,
I am confused about the difference between unloading of cores with
LotsOfCores and unloading a core with CoreAdmin.
From my understanding of LotsOfCores, if one
nloaded cores (call it
>> core21), that core is loaded (perhaps displacing one of the
>> currently-loaded cores) and the request is served.
>>
>> If core21 above had been unloaded with the core/admin command, then a
>> request directed to it would return an error instea
request is served.
If core21 above had been unloaded with the core/admin command, then a
request directed to it would return an error instead.
Best,
Erick
On Wed, Oct 22, 2014 at 12:11 PM, Xiaolu Zhao wrote:
Hi All,
I am confused about the difference between unloading of cores with
LotsOfCores and
ed, Oct 22, 2014 at 12:11 PM, Xiaolu Zhao wrote:
> Hi All,
>
> I am confused about the difference between unloading of cores with
> LotsOfCores and unloading a core with CoreAdmin.
>
> From my understanding of LotsOfCores, if one core is removed from transient
> cache, it is pendi
Hi All,
I am confused about the difference between unloading of cores with
LotsOfCores and unloading a core with CoreAdmin.
From my understanding of LotsOfCores, if one core is removed from
transient cache, it is pending to close, it means close all resources
allocated by the core if it is
Hi All,
I am confused about the difference between unloading of cores with
LotsOfCores and unloading a core with CoreAdmin.
From my understanding of LotsOfCores, if one core is removed from
transient cache, it is pending to close, it means close all resources
allocated by the core if it is
