Return-Path: X-Original-To: apmail-lucene-solr-user-archive@minotaur.apache.org Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 25F23108FD for ; Tue, 5 Nov 2013 11:07:57 +0000 (UTC) Received: (qmail 72184 invoked by uid 500); 5 Nov 2013 11:07:52 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 68962 invoked by uid 500); 5 Nov 2013 11:07:47 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 67881 invoked by uid 99); 5 Nov 2013 11:07:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Nov 2013 11:07:43 +0000 X-ASF-Spam-Status: No, hits=2.3 required=5.0 tests=FORGED_YAHOO_RCVD,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Nov 2013 11:07:38 +0000 Received: from ben.nabble.com ([192.168.236.152]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1VdeTd-0004Is-0i for solr-user@lucene.apache.org; Tue, 05 Nov 2013 03:07:17 -0800 Date: Tue, 5 Nov 2013 03:07:17 -0800 (PST) From: "michael.boom" To: solr-user@lucene.apache.org Message-ID: <1383649637013-4099378.post@n3.nabble.com> Subject: SolrCloud statistics MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org 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.