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

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

[~niqbal], Every time I restart 6.6.0, I see the problem described in this 
issue.

Version 6.6.1 may have a separate issue in addition to this issue, described in 
SOLR-11361.  I saw a similar message in the logs with 6.6.2-SNAPSHOT, and in 
that version, some of my cores that do not work at all.  For the problem I have 
described here, every core actually works, I just get annoying notifications in 
the admin UI and errors in the log.


> 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: 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to