Hi all, I'm facing an issue regarding custom code inside a .system-collection and starting up a Solr Cloud cluster. I thought, like its stated in the documentation, that in case using the .system collection custom code is lazy loaded, because it can happen that a collection that uses custom code is initialized before the system collection is up and running.
I did all the necessary configuration and while debugging, I can see that the custom code is wrapped via a PluginBag$LazyPluginHolder. So far its seems good, but I still get Exceptions when starting the Solr Cloud with the following errors: SolrException: Blob loading failed: .no active replica available for .system collection... In my case I'm using custom code for a couple of UpdateProcessors. So it seems, that this lazy mechanism is not working well for UpdateProcessors. Inside the calzz LazyPluginHolder the comment says: "A class that loads plugins Lazily. When the get() method is invoked the Plugin is initialized and returned." When a core is initialized and you have a custom UpdateProcessor, the get-method is invoked directly and the lazy loading mechanism tries to get the custom class from the MemClassLoader, but in most scenarios the system collection is not up and the above Exception is thrown... So maybe it’s the case that for UpdateProcessors while initializing a core, the routine is not implemented optimal for the lazy loading mechanism? Pls let me know if it helps sharing my configuration! Many thanks, Johannes
