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 332541728C for ; Wed, 6 May 2015 01:09:05 +0000 (UTC) Received: (qmail 86014 invoked by uid 500); 6 May 2015 01:09:01 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 85966 invoked by uid 500); 6 May 2015 01:09:01 -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 85954 invoked by uid 99); 6 May 2015 01:09:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 May 2015 01:09:00 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=FREEMAIL_REPLY,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of erickerickson@gmail.com does not designate 54.191.145.13 as permitted sender) Received: from [54.191.145.13] (HELO mx1-us-west.apache.org) (54.191.145.13) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 May 2015 01:08:55 +0000 Received: from mail-ie0-f169.google.com (mail-ie0-f169.google.com [209.85.223.169]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 5EDDF24E99 for ; Wed, 6 May 2015 01:08:35 +0000 (UTC) Received: by iedfl3 with SMTP id fl3so3631817ied.1 for ; Tue, 05 May 2015 18:07:59 -0700 (PDT) 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=3+keP1mjRumqNwhmAy34/Wo+CKv2I6DS0HhWTU1FE/o=; b=yHIF3nQ8zzO6IoT+Hu3qAovEmgxXL96qftGmlJs5BbefVgg71oLYTXKbNZ7OPeu9CH s0IL/cSu9qOv+W+E5kNAqZnGS2OjGVtW0a/p4OOVpy0/iSDrM4kkgNXkaWCXFki6KnTJ MReQCs1xToetMnSxC1G9Jotp44/C0oPemr40X9esjaWoMydaToN/eH9iqpnPcpsFxwK4 bZZ6AILRvk2xGhoPGXOh+MDJpXyXWbAkJB3eY/aAed3hpSlSt13dik7s3gJP2ONkukeR TWZr7FyoAndHX942Xm09z72EHTTmXcQ59RfM8/FBmCaH6XYHchNfEjXE76w/7GgCxL1n +6Yw== MIME-Version: 1.0 X-Received: by 10.50.178.133 with SMTP id cy5mr5280098igc.5.1430874479781; Tue, 05 May 2015 18:07:59 -0700 (PDT) Received: by 10.107.181.146 with HTTP; Tue, 5 May 2015 18:07:59 -0700 (PDT) In-Reply-To: References: Date: Tue, 5 May 2015 18:07:59 -0700 Message-ID: Subject: Re: SolrCloud indexing From: Erick Erickson To: solr-user@lucene.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org bq: Does it mean that all the indexing is done by the leaders in one node? no. The raw document is forwarded from the leader to the replica and it's indexed on all the nodes. The leader has a little bit of extra work to do routing the docs, but that's it. Shouldn't be a problem with 3 shards. bq: If so, how do I distribute the indexing (the shard leaders) across nodes? You don't really need to bother I don't think, especially if you don't see significantly higher CPU utilization on the leader. If you absolutely MUST distribute leadership, see the Collections API and the REBALANCELEADERS and BALANCESHARDUNIQUE (Solr 5.1 only) but frankly I wouldn't worry about it unless and until you had demonstrated need. Best, Erick On Tue, May 5, 2015 at 6:28 AM, Vincenzo D'Amore wrote: > Hi all, > > I have 3 nodes and there are 3 shards but looking at solrcloud admin I see > that all the leaders are on the same node. > > If I understood well looking at solr documentation > > : > >> When a document is sent to a machine for indexing, the system first >> determines if the machine is a replica or a leader. >> If the machine is a replica, the document is forwarded to the leader for >> processing. >> If the machine is a leader, SolrCloud determines which shard the document >> should go to, forwards the document the leader for that shard, indexes the >> document for this shard, and forwards the index notation to itself and any >> replicas. > > > So I have 3 nodes, with 3 shards and 2 replicas of each shard. > > http://picpaste.com/pics/Screen_Shot_2015-05-05_at_15.19.54-Xp8uztpt.1430832218.png > > Does it mean that all the indexing is done by the leaders in one node? If > so, how do I distribute the indexing (the shard leaders) across nodes? > > > -- > Vincenzo D'Amore > email: v.damore@gmail.com > skype: free.dev > mobile: +39 349 8513251