[SOLR-16899] CoreAdminOp are statically registered in CoreAdminHandler, preventing more than one Solr instance in the same JVM

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 9.2.1
• Fix Version/s: 9.4
• Assignee: Alex Deparvu
• Reporter: Cédric Damioli
• Created: 19/Jul/23 14:56
• Updated: 15/Oct/23 19:57
• Resolved: 12/Sep/23 21:26

Description

Since Solr 9.1 and SOLR-16282, one may register custom CoreAdminOp in solr.xml

Custom CoreAdminOp are stored in a static Map in CoreAdminHandler

Before 9.1 I could write eg. unit tests, each test starting its own EmbeddedSolrServer

Since 9.1, the second EmbeddedSolrServer try to load its own CoreAdminHandler and fail, complaining that the CoreAdminOp are already registered

I actually wonder if it's a bug or a feature, or an implementation constraint, but I don't have found any convenient workaround other than removing my custom CoreAdminOp, going back to the old way of subclassing the CoreAdminHandler 

Issue Links

• links to: GitHub Pull Request #1892