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 B1C0210416 for ; Mon, 22 Apr 2013 11:05:52 +0000 (UTC) Received: (qmail 33444 invoked by uid 500); 22 Apr 2013 11:05:49 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 33376 invoked by uid 500); 22 Apr 2013 11:05:49 -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 33357 invoked by uid 99); 22 Apr 2013 11:05:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Apr 2013 11:05:48 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of erickerickson@gmail.com designates 209.85.220.170 as permitted sender) Received: from [209.85.220.170] (HELO mail-vc0-f170.google.com) (209.85.220.170) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Apr 2013 11:05:44 +0000 Received: by mail-vc0-f170.google.com with SMTP id hv10so2398223vcb.15 for ; Mon, 22 Apr 2013 04:05:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=9EalWEu4kwmsb8YfnAZnmGde7rIz0hbo7GqQ5WzbSOU=; b=RO+MY77P7ndaC2wCgXKY7eIJCQ/C59aW0y214K0g96vRjEFW30ZGqvkWPN4d+H7BLW Gp6a3HQj54wnSGBoLAVAwNCZ6ZdN7uRwoFo4P0Rww9Mv6UBbCoPLtK4tM2OVhZqcLh4F 7oM+LxPczvm2UyzXnGXt5uoQRS2H+5AiEUlxhoD2EFG5WiJ68ciXPM5D7Dv6HZGSJz5f PThN1oJ23NBFuZ2HeSddwMoGwkkBqz67xfe/dFAiVzmxVZfR1ql93jH7ejgMu1Z3J9gd gIXoySwvQsgkr624gXuuPqCKkEHmSJPvR3oidFTkEz/vqMsNzll2fSal540+y6Y2zxTk GOpg== MIME-Version: 1.0 X-Received: by 10.220.248.200 with SMTP id mh8mr18530354vcb.51.1366628723615; Mon, 22 Apr 2013 04:05:23 -0700 (PDT) Received: by 10.52.77.66 with HTTP; Mon, 22 Apr 2013 04:05:23 -0700 (PDT) In-Reply-To: References: Date: Mon, 22 Apr 2013 07:05:23 -0400 Message-ID: Subject: Re: Solr cloud and batched updates From: Erick Erickson To: solr-user@lucene.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Thanks Yonik! You see how behind the times I get.... On Sun, Apr 21, 2013 at 5:07 PM, Timothy Potter wrote: > That's awesome! Thanks Yonik. > > Tim > > On Sun, Apr 21, 2013 at 1:30 PM, Yonik Seeley wrote: >> On Sun, Apr 21, 2013 at 11:57 AM, Timothy Potter wrote: >>> There's no problem here, but I'm curious about how batches of updates >>> are handled on the Solr server side in Solr cloud? >>> >>> Going over the code for DistributedUpdateProcessor and >>> SolrCmdDistributor, it appears that the batch is broken down and docs >>> are processed one-by-one. By processed, I mean that each doc in the >>> batch from the client is sent to replicas individually. >>> >>> This makes sense but I wonder if the forwarding on to replicas could >>> be done in sub-batches? >> >> Good news... they already are sent in batches! The docs are processed >> one-by-one, but then buffered (into batches) for forwarding to >> replicas. >> >> -Yonik >> http://lucidworks.com