Re: Collections API Overseer Status
+1 I was trying to understand a reload collection time out happening lately in a Solr Cloud cluster, and the Overseer Status was hard to decipher. More Human Readable names and some additional documentation could help here. Cheers - --- Alessandro Benedetti Search Consultant, R Software Engineer, Director Sease Ltd. - www.sease.io -- View this message in context: http://lucene.472066.n3.nabble.com/Collections-API-Overseer-Status-tp4345454p4345567.html Sent from the Solr - User mailing list archive at Nabble.com.
Collections API Overseer Status
Looking at the overseer API call as documented in the Solr Collections API https://cwiki.apache.org/confluence/display/solr/Collections+API#CollectionsAPI-OVERSEERSTATUS:OverseerStatusandStatistics The information returned looks like it could be useful in diagnosing problems with Solrcloud. It would be useful to document the metrics it returns What constitutes an "overseer operation"? What is "peek_wait_forever" ? I could go on but it's difficult to interpret the results of this API without more documentation -- This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person. If you have received this transmission in error, please notify the sender immediately and delete the message and any attachment from your system. Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not accept liability for any omissions or errors in this message which may arise as a result of E-Mail-transmission or for damages resulting from any unauthorized changes of the content of this message and any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not guarantee that this message is free of viruses and does not accept liability for any damages caused by any virus transmitted therewith. Click http://www.emdgroup.com/disclaimer to access the German, French, Spanish and Portuguese versions of this disclaimer.
Re: Collections API Overseer status and statistics
On 4/30/2015 11:22 AM, Ryan Steele wrote: What time unit is the Solr collections API overseerstatus action using in the returned data? For example, given the following XML: double name=avgTimePerRequest0.15491020578778136/double Is the avgTimePerRequest in seconds? Most timing data in Solr is reported in milliseconds, but if the sample data shown for OVERSEERSTATUS in the reference guide is from an actual response, I think these stats must be different, and reporting in seconds. If that's true, then we have an inconsistency, and it's my opinion that it should be changed to milliseconds. Thanks, Shawn
Collections API Overseer status and statistics
What time unit is the Solr collections API overseerstatus action using in the returned data? For example, given the following XML: double name=avgTimePerRequest0.15491020578778136/double Is the avgTimePerRequest in seconds? Thanks, Ryan --- This email has been scanned for email related threats and delivered safely by Mimecast. For more information please visit http://www.mimecast.com ---
Re: Collections API Overseer status and statistics
HI Ryan, That is in milliseconds. On Thu, Apr 30, 2015 at 10:52 PM, Ryan Steele ryan.ste...@pgi.com wrote: What time unit is the Solr collections API overseerstatus action using in the returned data? For example, given the following XML: double name=avgTimePerRequest0.15491020578778136/double Is the avgTimePerRequest in seconds? Thanks, Ryan --- This email has been scanned for email related threats and delivered safely by Mimecast. For more information please visit http://www.mimecast.com --- -- Regards, Shalin Shekhar Mangar.
