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 AC4E17089 for ; Tue, 20 Sep 2011 22:10:45 +0000 (UTC) Received: (qmail 91780 invoked by uid 500); 20 Sep 2011 22:10:42 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 91742 invoked by uid 500); 20 Sep 2011 22:10:42 -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 91734 invoked by uid 99); 20 Sep 2011 22:10:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Sep 2011 22:10:42 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rcmuir@gmail.com designates 209.85.215.176 as permitted sender) Received: from [209.85.215.176] (HELO mail-ey0-f176.google.com) (209.85.215.176) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Sep 2011 22:10:36 +0000 Received: by eyb7 with SMTP id 7so808764eyb.35 for ; Tue, 20 Sep 2011 15:10:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; bh=6sdYem9WH5d2z9QO+HayN/MK28hgl7+NE/Chw9r5QVg=; b=ufZcvlOVLmcNH8oRVMTCRIY3eIWSlV7zVScerIzapUcxkG6/F6TcgX7Gse0tPKIw4u t4O9AYvxJgXVI0TIdpJDCyxRwQ4pPsnmsXAxZunRCe4YpSxBU64W2TcevsNEO7ZvdOvn dD+YakSHSDO3mTvwqlzHqgfAvuGGoCfI5hxg0= Received: by 10.216.80.1 with SMTP id j1mr1408457wee.44.1316556616197; Tue, 20 Sep 2011 15:10:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.20.5 with HTTP; Tue, 20 Sep 2011 15:09:56 -0700 (PDT) In-Reply-To: References: From: Robert Muir Date: Tue, 20 Sep 2011 15:09:56 -0700 Message-ID: Subject: Re: Example setting TieredMergePolicy for Solr 3.3 or 3.4? To: solr-user@lucene.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Mon, Sep 19, 2011 at 9:57 AM, Burton-West, Tom wrot= e: > Thanks Robert, > > Removing "set" from " setMaxMergedSegmentMB" and using "maxMergedSegmentM= B" fixed the problem. > ( Sorry about the multiple posts. =C2=A0Our mail server was being flaky a= nd the client lied to me about whether the message had been sent.) > > I'm still confused about the mergeFactor=3D10 setting in the example conf= iguration. =C2=A0Took a quick look at the code, but I'm obviously looking i= n the wrong place. Is mergeFactor=3D10 interpreted by TieredMergePolicy as > segmentsPerTier=3D10 and maxMergeAtOnce=3D10? =C2=A0 If I specify values = for these is the mergeFactor setting ignored? Sorry, I just now noticed you responded! yes, mergeFactory=3D10 is interpreted as both segmentsPerTier and maxMergeA= tOnce. yes, specifying explicit TieredMP parameters will override whatever you set in mergeFactor (which is basically only interpreted to be backwards compatible) this is why i created this confusing test configuration: to test this exact case. --=20 lucidimagination.com