[
https://issues.apache.org/jira/browse/SOLR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528851
]
Hoss Man commented on SOLR-256:
-------------------------------
proposed solrconfig.xml syntax...
<jmx />
...wraps the solr registry stuff in MBeans, adds them to the first MBeanSearver
it finds (if any) but will not create one.
<jmx agentId="foo" />
...wraps the solr registry stuff in MBeans, adds them to the first MBeanServer
it finds matching that agentId, error if MBeanServer can't be found.
<jmx serviceurl="service:jmx:rmi:///jndi/rmi://localhost:9999/solr" />
...wraps the solr registry stuff in MBeans, foracbly spins up a new MBeanServer
exposed for remote monitoring at the specific service url, if the
JMXConnectorServer can't be started (probably because the serviceurl is bad)
then error.
(we can punt on the issue of security -- if users want Solr to manage their JMX
remote debuging then it's wide open; if you want password files or ssl, then
configure that with the JVM system properties for remote debugging and just
tell solr "<jmx />")
> 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
> Priority: Minor
> Attachments: jmx.patch, jmx.patch, jmx.patch, jmx.patch, jmx.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)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
