Pasquale,
Are you using any custom written components anywhere in your solrconfig?
It's possible that in your custom code you are calling getCore() on a
SolrQueryRequest object and then calling a close() on that core. Since
getCore() doesn't increment the ref count of the core AND core.close()
decrements it, this could be a possible cause of your issue.
(This is tricky since a getCore() on a core container object DOES increment
the ref count and so you need to call core.close() when done with the core
from CoreContainer object)

Also, do you see a "SolrCoreState already closed" exception anywhere in the
logs?

-Rahul



On Wed, Oct 20, 2021 at 11:15 AM Atita Arora <atitaar...@gmail.com> wrote:

> Hi,
>
> I once had this issue too , not sure , are you also writing intensively ?
> Looking at the code too , it looks like it's just trying to close the
> writer stream and related resources
> searcher / updatehandler .
> Although I do see https://issues.apache.org/jira/browse/SOLR-4753 as well
> open.
> As the code says (from where the error message originated) on close :
>
> If reference count is > 0, the usage count is decreased by 1 and no
> resources are released.
> If reference count is == 0, the resources are released.
> If reference count is < 0, and error is logged and no further action
> * is taken.
>
> HTH.
>
>
> On Wed, Oct 20, 2021 at 3:55 PM Pasquale Moramarco <p.morama...@reply.it>
> wrote:
>
>> Hi,
>>
>>
>>
>> I’m using solr and I have this issue:
>>
>>
>>
>> 20/10/2021, 15:29:44
>>
>> ERROR true
>>
>> x:product-hash_shard1_replica_n1
>>
>> SolrCore
>>
>> Too many close [count:-22] on org.apache.solr.core.SolrCore@6d0f1fd4.
>> Please report this exception to solr-u...@lucene.apache.org
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> This is my solr installation:
>>
>>
>>
>> Can you help me to understand this kind of error and the possible
>> resolution?
>>
>>
>>
>> Thanks,
>>
>> Pasquale
>>
>>
>> Pasquale Moramarco
>>
>> Blue Reply
>> Via Giuseppe Sangiorgi, 15
>> 70124 - Bari - ITALY
>> phone: +39 080 9727039
>> p.morama...@reply.it
>> www.reply.it
>>
>> [image: Blue Reply]
>>
>

Reply via email to