[
https://issues.apache.org/jira/browse/SOLR-11297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16179465#comment-16179465
]
Shawn Heisey commented on SOLR-11297:
-------------------------------------
bq. so, all this stuff about patching is this in a Solr 6.1.x download?
It's just a patch attached to a Jira issue right now. To be seen in a
downloaded version, a change must be committed to one or more code branches,
and then somebody must volunteer to be the release manager for a new version
built from a branch with the fix.
At this time, I think the earliest release that *might* get this issue resolved
will be 7.1.0. The problems seen in SOLR-11361 (which I think Erick's patch
also fixes) might be severe enough to justify a 6.6.2 release, but that's not
something I would count on.
Side note: Just like a user on IRC, I was having a problem accessing
/solr/admin/metrics with 6.6.0 and a 6.6.2-SNAPSHOT version that I had built
previously, but that problem seems to be fixed now. I do not know if Erick's
patch is what made that work, or if it was another change made to the 6.6
branch.
> 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
