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

Shawn Heisey commented on SOLR-11297:
-------------------------------------

With the latest patch applied to branch_6_6 and installing from 
solr-6.6.2-SNAPSHOT.tgz, everything works as expected.  There are no errors in 
the admin UI, and the "Lock held by this virtual machine" message is not in the 
log.  The only errors I see in the log are those generated by accessing cores 
while they are loading.

{code}
<title>Error 503 
{metadata={error-class=org.apache.solr.common.SolrException,root-error-class=org.apache.solr.common.SolrException},msg=SolrCore
 is loading,code=503}</title>
{code}


> 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.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.
> One critical detail to this issue: The cores are all perfectly functional.  
> If somebody is seeing an error message that results in a core not working at 
> all, then it is likely a different issue.



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