[
https://issues.apache.org/jira/browse/SOLR-7667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583587#comment-14583587
]
Junhao Li commented on SOLR-7667:
---------------------------------
Reason:
-----------------------
Read the log, you will find core1, core2, core3, core4 are closing —- But
actually they are not.
In Solr code, you will find core1-4 are just remove from the list in core
container. But the actual closing operation are not done. Because the closer
thread are hang!
How to bypass it:
-----------------------
There may be plenty ways to bypass this bug. And I am listing the 1 way:
make sure there is at lease one transient core(let call it “SaviorCore”)
who is loadOnStarup=False
When the Situation described above happen, send luke/mbean/any request to
load “SaviorCore”. Then you will find core1, core2, core3, core4 are actually
closed in the JConsole.
> If more cores are loaded at startup than the transient core size, cores
> become unavailable.
> -------------------------------------------------------------------------------------------
>
> Key: SOLR-7667
> URL: https://issues.apache.org/jira/browse/SOLR-7667
> Project: Solr
> Issue Type: Bug
> Affects Versions: 5.2.1, Trunk
> Reporter: Erick Erickson
> Assignee: Erick Erickson
>
> Edwin Lee from the user's list caught this, the original post is titled
> "loadOnStartup & transientCoreSize & BUG Report on CoreContainer.java"
> Nice catch Edwin!
> More details to follow:
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
