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 E7105102C7 for ; Thu, 7 Nov 2013 12:27:43 +0000 (UTC) Received: (qmail 77401 invoked by uid 500); 7 Nov 2013 12:27:33 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 77349 invoked by uid 500); 7 Nov 2013 12:27:32 -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 77339 invoked by uid 99); 7 Nov 2013 12:27:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Nov 2013 12:27:32 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of erickerickson@gmail.com designates 209.85.212.50 as permitted sender) Received: from [209.85.212.50] (HELO mail-vb0-f50.google.com) (209.85.212.50) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Nov 2013 12:27:26 +0000 Received: by mail-vb0-f50.google.com with SMTP id x16so314057vbf.9 for ; Thu, 07 Nov 2013 04:27:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=MeuKaF2x0JXquvvJtHQl28dGc48Xa+6CJiI/BkXiv+E=; b=mclxaSRN6+bdDK7ovaIAnX5BInAESGK4Gs69HAeydwjPbw+9Q6FNUNPNk73tLDrMOO F+7SapERiRUcvhj+ysX1OySL5AAbiNkJ5JQhJqmRVQIomZNjkVhFHQ9W6+ZbqFFhN5os hPzNVoivmsc6GvzY2E5tHO90mhdoON94Wgf00MCuUXZvTw94bheoUCJoSgn3a7OgU9FR THq47HkrjBVAJasFfvwzgEMYrBnS4Sr0NqSxNz6Gl6/0/RS3FrwQ+SzrdNK7MftlVnSy QnoE90mv8LMp+G6LpFfQZYVM6rg80QpR2LZkACp5+Tf7rgGTguM4D4fkBCjskZKQWvNu qXNw== MIME-Version: 1.0 X-Received: by 10.220.10.70 with SMTP id o6mr312034vco.45.1383827225237; Thu, 07 Nov 2013 04:27:05 -0800 (PST) Received: by 10.52.171.78 with HTTP; Thu, 7 Nov 2013 04:27:05 -0800 (PST) In-Reply-To: <1383649637013-4099378.post@n3.nabble.com> References: <1383649637013-4099378.post@n3.nabble.com> Date: Thu, 7 Nov 2013 07:27:05 -0500 Message-ID: Subject: Re: SolrCloud statistics From: Erick Erickson To: solr-user@lucene.apache.org Content-Type: multipart/alternative; boundary=001a11c3b87830eab604ea956232 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c3b87830eab604ea956232 Content-Type: text/plain; charset=ISO-8859-1 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 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. > --001a11c3b87830eab604ea956232--