[
https://issues.apache.org/jira/browse/SOLR-10020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson resolved SOLR-10020.
-----------------------------------
Resolution: Fixed
Fix Version/s: 6.5
trunk
[[email protected]][[email protected]][~ichattopadhyaya] I had some merge
issues when I merged CHANGES.txt from trunk to 6x for this JIRA. It seems like
some entries were moved around in trunk (SOLR-10114) in CHANGES.txt but not
merged into the 6x version.
So the changes from around SOLR-10114 through "optimizations" for the 6.5
version of solr/CHANGES.txt where I had the unexpected conflict looks OK to me,
this is just a heads-up in case I messed up the merge and you wanted to take a
look.
> CoreAdminHandler silently swallows some errors
> ----------------------------------------------
>
> Key: SOLR-10020
> URL: https://issues.apache.org/jira/browse/SOLR-10020
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Fix For: trunk, 6.5
>
> Attachments: SOLR-10020.patch, SOLR-10020.patch, SOLR-10020.patch,
> SOLR-10020.patch
>
>
> With the setup on SOLR-10006, after removing some index files and starting
> that Solr instance I tried issuing a REQUESTRECOVERY command and it came back
> as a success even though nothing actually happened. When the core is
> accessed, a core init exception is returned by subsequent calls to getCore().
> There is no catch block after the try so no error is returned.
> Looking through the code I see several other commands that have a similar
> pattern:
> FORCEPREPAREFORLEADERSHIP_OP
> LISTSNAPSHOTS_OP
> getCoreStatus
> and perhaps others. getCore() can throw an exception, about the only explicit
> one it does throw is if the core has an initialization error.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
