[ https://issues.apache.org/jira/browse/SOLR-7159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vamsee Yarlagadda updated SOLR-7159: ------------------------------------ Attachment: SOLR-7159v2.patch Screen Shot 2015-02-25 at 2.05.45 PM.png Screen Shot 2015-02-25 at 2.05.34 PM.png [~elyograg] Thanks for the feedback. * Updated my patch to refer to the trunk. * The reason why i ended up putting under core is because every core instance has its own update and query httpclients. So i thought having it as part of core stats makes more sense. I am open for more feedback here. * I followed this wiki (https://wiki.apache.org/solr/SolrJmx) to see the JMX stats (latest screenshots attached) * Looks like even Solr admin web ui uses the MBeans to populate the stats. That being said, the existing patch also shows stats on the solr web ui :) (screenshot attached) > Add httpclient connection stats to JMX report > --------------------------------------------- > > Key: SOLR-7159 > URL: https://issues.apache.org/jira/browse/SOLR-7159 > Project: Solr > Issue Type: Improvement > Affects Versions: 4.10.3 > Reporter: Vamsee Yarlagadda > Priority: Minor > Attachments: SOLR-7159.patch, SOLR-7159v2.patch, Screen Shot > 2015-02-25 at 2.05.34 PM.png, Screen Shot 2015-02-25 at 2.05.45 PM.png > > > Currently, we are logging the stats of httpclient as part of debug level. > bq. 2015-01-20 13:47:48,640 DEBUG > org.apache.http.impl.conn.PoolingClientConnectionManager: Connection request: > [route: {}->http://plh04.wil.csc.local:8983][total kept alive: 254; route > allocated: 100 of 100; total allocated: 462 of 10000] > Instead, it would be good to expose these metrics via JMX for easy checking. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org