Return-Path: 
 <solr-user-return-97923-apmail-lucene-solr-user-archive=lucene.apache.org@lucene.apache.org>
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 4AC4AC5E0
	for <apmail-lucene-solr-user-archive@minotaur.apache.org>;
 Mon, 10 Mar 2014 13:57:59 +0000 (UTC)
Received: (qmail 6303 invoked by uid 500); 10 Mar 2014 13:57:54 -0000
Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org
Received: (qmail 6248 invoked by uid 500); 10 Mar 2014 13:57:53 -0000
Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:solr-user-help@lucene.apache.org>
List-Unsubscribe: <mailto:solr-user-unsubscribe@lucene.apache.org>
List-Post: <mailto:solr-user@lucene.apache.org>
List-Id: <solr-user.lucene.apache.org>
Reply-To: solr-user@lucene.apache.org
Delivered-To: mailing list solr-user@lucene.apache.org
Received: (qmail 6236 invoked by uid 99); 10 Mar 2014 13:57:53 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Mar 2014 13:57:53 +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 furkankamaci@gmail.com
 designates 209.85.219.54 as permitted sender)
Received: from [209.85.219.54] (HELO mail-oa0-f54.google.com) (209.85.219.54)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Mar 2014 13:57:47 +0000
Received: by mail-oa0-f54.google.com with SMTP id n16so7025013oag.41
        for <solr-user@lucene.apache.org>;
 Mon, 10 Mar 2014 06:57:26 -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=vIXtheeBeUT7eIjBH6+Dwm9fQnTVEuRL4YzgyDdILqI=;
        b=vSrWCOi92yD16of83yKHVFqRHWXuzHYfeC75CL6/hsbWEZehLLu22f1lqBMaTeSnlE
         aktwgo+L3TIQFhgQdeFwDlmvZzTB7/9C0Vkhff6WgapgWi1cwF3bUjtXv2Y7Au8Bk4vh
         jYanV5Ew84n0MmmeTr7HQkMtAHg3mQQ4gyVNOhbT2rvIx8197RZDt75IKrYt+w5mzt37
         /lzqt4DX/d30R0+ujNdVpYBwBofZLtLfLHH4vHxJMVFTrGw2TSWIno1ttiWS+wZX2pcO
         lrQbqz6oCxP5moP+KT0ctfcRNMX/U8mGbYkcyGJ0o1UZBigBLapgEMxEyB9oA2lXld6h
         aCdw==
MIME-Version: 1.0
X-Received: by 10.182.43.161 with SMTP id x1mr28233160obl.5.1394459846494;
 Mon, 10 Mar 2014 06:57:26 -0700 (PDT)
Received: by 10.76.154.162 with HTTP; Mon, 10 Mar 2014 06:57:26 -0700 (PDT)
In-Reply-To: <1394457249446-4122558.post@n3.nabble.com>
References: <1394457249446-4122558.post@n3.nabble.com>
Date: Mon, 10 Mar 2014 15:57:26 +0200
Message-ID: 
 <CAHsXEHX9-PDd9X-MDBM8daFqStWKVOO0of6irX7Nik=YHGSD+A@mail.gmail.com>
Subject: Re: The way Autocommit works in solr - Wierd
From: Furkan KAMACI <furkankamaci@gmail.com>
To: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org>
Content-Type: multipart/alternative; boundary=001a11c30ce2cdd2e004f440fb9a
X-Virus-Checked: Checked by ClamAV on apache.org

--001a11c30ce2cdd2e004f440fb9a
Content-Type: text/plain; charset=ISO-8859-1

Hi;

Did you read here:
http://searchhub.org/2013/08/23/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/

Thanks;
Furkan KAMACI


2014-03-10 15:14 GMT+02:00 RadhaJayalakshmi <rlakshminarayanan@inautix.co.in
>:

> Hi,
>
> Brief Description of my application:
> We have a java program which reads a flat file, and adds document to solr
> using cloudsolrserver.
> And we index for every 1000 documents(bulk indexing).
>
> And the Autocommit setting of my application is:
> <autoCommit>
>         <maxDocs>100000</maxDocs>
>         <openSearcher>false</openSearcher>
> </autoCommit>
>
> So after every 100,000 documents are indexed, engine should perform a
> HardCommit/AutoCommit. But still the OpenSearcher will be false.
> Once the file is fully read, we are issuing a commit() from the
> CloudSolrServer class. So this by default opens a new Searcher.
>
> Also, from the Log, i can see that three times, Autocommit is happenning.
> and Only with the last/final Autocommit, opensearcher is set to true.
>
> So, till now all looks fine and working as expected.
>
> But one strange issue i observed during the course of indexing.
> Now, as per the documentation, the data that is being indexed should first
> get written into tlog. When the Autocommit is performed, the data will be
> flushed to disk.
> So only at three times, there should have been size difference in the
> /index
> folder. All the time only the size of the /tlog folder should have been
> changing
>
> But actually happened is, all the time, i see the size of the /index folder
> getting increased in parallel to the size of the /tlog folder.
> Actually it is increasing to certain limit and coming down. Again
> increasing
> and coming down to a point.
>
> So Now the bigger doubt is have is, during hard commit, is the data getting
> written into both /index or /tlog folder??
>
> I am using solr 4.5.1.
>
> Some one please clear me how the hardcommit works. I am asumming the
> following sequence:
> 1. Reads the data and writes to tlog
> 2. During hardcommit, flushes the data from tlog to index. If openSearcher
> is false, should not open a new searcher
> 3. In the end, once all the datas are indexed, it should open a new
> searcher.
>
> If not please explain me..
>
> Thanks in Advance
> Radha
>
>
>
>
>
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/The-way-Autocommit-works-in-solr-Wierd-tp4122558.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>

--001a11c30ce2cdd2e004f440fb9a--