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 E424E11CF2 for ; Fri, 25 Jul 2014 14:34:14 +0000 (UTC) Received: (qmail 95894 invoked by uid 500); 25 Jul 2014 14:34:06 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 95830 invoked by uid 500); 25 Jul 2014 14:34:06 -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 95806 invoked by uid 99); 25 Jul 2014 14:34:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Jul 2014 14:34:05 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Jul 2014 14:34:03 +0000 Received: from ben.nabble.com ([192.168.236.152]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1XAgZ0-0006MD-IH for solr-user@lucene.apache.org; Fri, 25 Jul 2014 07:33:38 -0700 Date: Fri, 25 Jul 2014 07:33:38 -0700 (PDT) From: ian To: solr-user@lucene.apache.org Message-ID: <1406298818559-4149219.post@n3.nabble.com> In-Reply-To: References: <20140708131520.B998944811F@nhs-pd1e-esg107.ad1.nhs.net> <1405416841108-4147183.post@n3.nabble.com> <1405518568001-4147481.post@n3.nabble.com> Subject: Re: Slow inserts when using Solr Cloud MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org I've built and installed the latest snapshot of Solr 4.10 using the same SolrCloud configuration and that gave me a tenfold increase in throughput, so it certainly looks like SOLR-6136 was the issue that was causing my slow insert rate/high latency with shard routing and replicas. Thanks for your help. Timothy Potter wrote > Hi Ian, > > What's the CPU doing on the leader? Have you tried attaching a > profiler to the leader while running and then seeing if there are any > hotspots showing. Not sure if this is related but we recently fixed an > issue in the area of leader forwarding to replica that used too many > CPU cycles inefficiently - see SOLR-6136. > > Tim -- View this message in context: http://lucene.472066.n3.nabble.com/Slow-inserts-when-using-Solr-Cloud-tp4146087p4149219.html Sent from the Solr - User mailing list archive at Nabble.com.