[
https://issues.apache.org/jira/browse/SOLR-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14128723#comment-14128723
]
Timothy Potter commented on SOLR-6504:
--------------------------------------
I'll take a look
> Switching exploded war from version 4.10 caused Solr to be unable to start
> --------------------------------------------------------------------------
>
> Key: SOLR-6504
> URL: https://issues.apache.org/jira/browse/SOLR-6504
> Project: Solr
> Issue Type: Bug
> Reporter: Brian
> Assignee: Timothy Potter
> Priority: Minor
>
> I tried upgrading to Solr 4.10 from Solr 4.8.1 by switching the server to use
> the new Solr 4.10 web application folder (exploded war) - simply by renaming
> the folder from "solr_4_10" to "solr" (and the previous "solr" to
> "solr_old"), then restarting the server.
> This worked fine, but there was an incompatibility forcing me to switch back
> to 4.8.1, which I did by renaming the folders again, "solr_old" back to
> "solr" and restarting the server.
> However on restart, none of the cores could load, giving the following error:
>
> org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
> java.util.ArrayList cannot be cast to java.util.Map
> By searching I found the previous issue (linked to below), and found this was
> the same problem - "_rest_managed.json" files were being created, and once I
> deleted them that particular error message went away and most cores could be
> loaded.
> I.e., this appears to be the same issue as:
> https://issues.apache.org/jira/browse/SOLR-6182
>
> except it is caused by a different process. Either that issue wasn't really
> resolved, or this is a different problem with the same symptoms.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
