Hi; I've written a patch to get Statistics from SolrCloud. However my implementation was based on Solrj and after I got feedback from Shalin Shekhar I come up to write a new patch that based on distributed search components. I can add that capability and improve my patch with that.
-- Thanks; Furkan KAMACI 2013/11/7 Erick Erickson <erickerick...@gmail.com> > Your servlet container logs often have this number, or your > app can easily record them, I don't know of another way > to do that. > > The variant here is that what's actually being reported is "QTime", > which is also exclusive of actually gathering up the data to put > in the return packet, it's just the raw time spend finding the result > set. > > I guess Solr could record the time from when it started working on > a request to the time it was finished, which would still be exclusive > of network transmission but closer to what you're asking. Want > to write a patch? > > Best, > Erick > > > On Tue, Nov 5, 2013 at 6:07 AM, michael.boom <my_sky...@yahoo.com> wrote: > > > Solr's queryhandler statistics are pretty neat. Avg time per req, avg > > requests in the last 5/15 min and so on. > > But, when using SolrCloud's distributed search each core gets multiple > > requests, making it hard to check which is the actual query time (the > time > > from when a leader gets the query request until the resultset is actually > > served back to the client). > > > > Is there a way to monitor this (or maybe a tool) ? > > > > > > > > ----- > > Thanks, > > Michael > > -- > > View this message in context: > > http://lucene.472066.n3.nabble.com/SolrCloud-statistics-tp4099378.html > > Sent from the Solr - User mailing list archive at Nabble.com. > > >
