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

Erick Erickson commented on SOLR-11297:
---------------------------------------

OK, I poked at this yesterday and my bright idea of moving things to 
createCoreFromDescriptor doesn't work. getCore is the problem, it depends on 
getting the core back from waitAddPendingCoreOps if some other thread is 
opening the core. If we put some kind of test in getCore instead (say 
isCoreInPending() or something), then later in that method called 
createCoreFromDescriptor (assuming the core wasn't in pending ops), it'd be 
possible that another process would open the core between the calls.

There are three places in CoreContainer that call createCoreFromDescriptor 
without being surrounded by a waitAddPendingCoreOps/removeFromPendingOps, I'm 
working up a patch for the other two.

We'll see if it fixes Shawn's problem too, vetting it a bit more now and will 
put up a patch later today if all goes well.

> Message "Lock held by this virtual machine" during startup.  Solr is trying 
> to start some cores twice
> -----------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-11297
>                 URL: https://issues.apache.org/jira/browse/SOLR-11297
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 6.6
>            Reporter: Shawn Heisey
>            Assignee: Erick Erickson
>         Attachments: SOLR-11297.patch, SOLR-11297.sh, solr6_6-startup.log
>
>
> Sometimes when Solr is restarted, I get some "lock held by this virtual 
> machine" messages in the log, and the admin UI has messages about a failure 
> to open a new searcher.  It doesn't happen on all cores, and the list of 
> cores that have the problem changes on subsequent restarts.  The cores that 
> exhibit the problems are working just fine -- the first core load is 
> successful, the failure to open a new searcher is on a second core load 
> attempt, which fails.
> None of the cores in the system are sharing an instanceDir or dataDir.  This 
> has been verified several times.
> The index is sharded manually, and the servers are not running in cloud mode.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to