Yes it is a feature :) Refer to Hoss's comment quoted below:
"is there any reason not to have the searcher's add/remove themselves using their true name on register()/close() *and* have register() call put("searcher", this) like you have it now? ... that way you'd get the benefits you mentioned before (continuous monitoring of the current searcher) but you could also get information about how many "live" searchers there currently are, and what their stats look like (so you could, for example, notice when there is a really old Searcher hanging around for some inexplicable reason, probably a bug.)" https://issues.apache.org/jira/browse/SOLR-256?focusedCommentId=12617632#action_12617632 On Sat, Aug 2, 2008 at 3:31 PM, Koji Sekiguchi <[EMAIL PROTECTED]> wrote: > After this committed, I can see two searchers registered at admin GUI, > due to the following lines on SolrIndexSearcher: > > @@ -171,6 +169,9 @@ > /** Register sub-objects such as caches > */ > public void register() { > + // register self > + core.getInfoRegistry().put("searcher", this); > + core.getInfoRegistry().put(name, this); > for (SolrCache cache : cacheList) { > cache.setState(SolrCache.State.LIVE); > core.getInfoRegistry().put(cache.name(), cache); > > Is this intentional? > > Koji > > > > Shalin Shekhar Mangar (JIRA) wrote: > >> [ >> https://issues.apache.org/jira/browse/SOLR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel] >> >> Shalin Shekhar Mangar resolved SOLR-256. >> ---------------------------------------- >> >> Resolution: Fixed >> >> Committed revision 680795. >> >> >> >>> Stats via JMX >>> ------------- >>> >>> Key: SOLR-256 >>> URL: https://issues.apache.org/jira/browse/SOLR-256 >>> Project: Solr >>> Issue Type: New Feature >>> Components: search, update >>> Reporter: Sharad Agarwal >>> Assignee: Shalin Shekhar Mangar >>> Priority: Minor >>> Fix For: 1.3 >>> >>> Attachments: jmx.patch, jmx.patch, jmx.patch, jmx.patch, >>> jmx.patch, SOLR-256.patch, SOLR-256.patch, SOLR-256.patch, SOLR-256.patch, >>> SOLR-256.patch, SOLR-256.patch, SOLR-256.patch, SOLR-256.patch, >>> SOLR-256.patch, SOLR-256.patch >>> >>> >>> This patch adds JMX capability to get statistics from all the >>> SolrInfoMBean. >>> The implementation is done such a way to minimize code changes. In >>> SolrInfoRegistry, I have overloaded Map's put and remove methods to >>> register and unregister SolrInfoMBean in MBeanServer. Later on, I am >>> planning to use register and unregister methods in SolrInfoRegistry and >>> removing getRegistry() method (Hiding the map instance to other classes) >>> >>> >> >> >> > > -- Regards, Shalin Shekhar Mangar.