[ https://issues.apache.org/jira/browse/SOLR-11297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16170333#comment-16170333 ]
Richard Rominger commented on SOLR-11297: ----------------------------------------- I can say for my test bed using 6.6.0 / 6.6.1 it's pretty reproducible. I am running Windows 10 1703 for my testing. I go back to 6.2.1 and it stable as a rock. When the problem kicks in, all I have to do is shutdown Solr and restart it on a different port and it loads up fine. Then I shutdown for a bit of time and I can then restart on the port that I really want Solr running on. > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org