[ https://issues.apache.org/jira/browse/SOLR-5095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725020#comment-13725020 ]
Alan Woodward commented on SOLR-5095: ------------------------------------- Possibly related: https://issues.apache.org/jira/browse/SOLR-4735 > SolrCore.infoRegistry needs overhauled with some form of "namespacing" > ---------------------------------------------------------------------- > > Key: SOLR-5095 > URL: https://issues.apache.org/jira/browse/SOLR-5095 > Project: Solr > Issue Type: Bug > Reporter: Hoss Man > Attachments: SOLR-5095_bug_demo.patch > > > While investigating SOLR-3616 / SOLR-2715, I realized the failure i was > seeing didn't seem to be related to the initial report of that bug, and > instead seemed to be due to an obvious and fundemental limitation in the way > SolrCore keeps track of "plugins" using the infoRegistry: It's just a > {{Map<String, SolrInfoMBean>}} keyed off of the name of the plugin, but there > is not "namespacing" used in the infoRegistry, so two completley different > types of plugins with the same name will overwrite each other. > When looking at data using something like /admin/mbeans, this manifests > itself solely as missing objects: last one .put() into the infoRegistry > "wins" -- using JMX, both objects are actually visible because of how JMX > ObjectNames are built arround a set of key=val pairs, and a bug in how > JmxMonitorMap unregisters existing MBeans when .put() is called on a key it > already knows about (the unregister call is made using an ObjectName built > using the infoBean passed to the put() call -- if infoBean.getName() is not > exactly the same as the previous infoBean put() with the same key, then the > MbeanServer will continue to know about both of them) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org