[ 
https://issues.apache.org/jira/browse/SOLR-7667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14584630#comment-14584630
 ] 

Junhao Li commented on SOLR-7667:
---------------------------------

In my understanding,
1. when loadOnStarup transientCores > transientCacheSize, I think it is a 
reasonable configuration. In our project, we would like to monitor the solr 
core state, we have to load the core one by one to get the snapshot of it. So 
load it one by one make sense to us.
2. The loadOnStartup is only one of the problem of it. The problem is "improper 
core close" operation. This bug is haunting solr whenever there is core closing 
involved.

And...

The reason why it keep happenning on "loadOnStartup=true" mainly because the 
closeThread initialize after the all of transient cores creation.

In CoreContainter.java

      try {
        coreLoadExecutor.invokeAll(creators);
      }
      catch (InterruptedException e) {
        throw new SolrException(SolrException.ErrorCode.SERVICE_UNAVAILABLE, 
"Interrupted while loading cores");
      }

      // Start the background thread
      backgroundCloser = new CloserThread(this, solrCores, cfg);
      backgroundCloser.start();

    } finally {
      ExecutorUtil.shutdownNowAndAwaitTermination(coreLoadExecutor);
    }


> 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]

Reply via email to