Return-Path: X-Original-To: apmail-lucene-java-user-archive@www.apache.org Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 65EEA1098E for ; Tue, 4 Nov 2014 15:48:53 +0000 (UTC) Received: (qmail 14703 invoked by uid 500); 4 Nov 2014 15:48:51 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 14638 invoked by uid 500); 4 Nov 2014 15:48:51 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Received: (qmail 14626 invoked by uid 99); 4 Nov 2014 15:48:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Nov 2014 15:48:51 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.215.44] (HELO mail-la0-f44.google.com) (209.85.215.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Nov 2014 15:48:47 +0000 Received: by mail-la0-f44.google.com with SMTP id gf13so1110323lab.31 for ; Tue, 04 Nov 2014 07:47:40 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=/igF4RWY2u3j3LwOR0WBujtoaGhkaozozcyJJ7SIaJc=; b=lgFQbchqzxEXskbCPWppOEDbRThjN+aJmsLpR+29Nr2bD9TkXa60oBspgz3SqR+3tf cP3BFl8Yrit+oK8IeuabRxKeWO4Wb4aV0s8VJigwmwBWFCaJrxz8mytygaeGjX2Qo64N gu3E7RYo3qjog3JjoQa0fzlGa2ApR+h/mTLIwvvrnjPLPmbDEurfzLXmAXyVXPnxZtpU ZGmVhgSmxNc6CY+pbd48Yj5gfNsyVbP+YB4MASN1JpMhQP/cNnkbC2naIka5DY5WXMBr hkPJwdSlUKcZ8U5fMtowjV4DnZCp9qA4aT3s4Jx2qsNlmkpE/95jt36Ty7k6qQPt66lM Qc1w== X-Gm-Message-State: ALoCoQlJychFFxAJMp6tTvxZF8lSd85LbxhoYp9tkVMSFe4vJFsEljU9E18aib2jUDJXpR4c/6uP X-Received: by 10.112.201.72 with SMTP id jy8mr17376525lbc.65.1415116059344; Tue, 04 Nov 2014 07:47:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.22.158 with HTTP; Tue, 4 Nov 2014 07:47:17 -0800 (PST) In-Reply-To: References: From: Michael McCandless Date: Tue, 4 Nov 2014 10:47:17 -0500 Message-ID: Subject: Re: When does a segment file gets written... To: Lucene Users Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org Call commit. Mike McCandless http://blog.mikemccandless.com On Tue, Nov 4, 2014 at 8:28 AM, Shouvik Bardhan wrote: > Apologies if this is trivial but I have read what I could on the net and > could not come up with a good answer. > > I have stood up a lucene server (not solr) which listens on 2 ports - one > for indexing and one for search. Also on different threads. The indexer > threads use one IndexWriter and the searcher threads get the > SearcherManager from the Indexwriter and does maybereopen() to refresh from > time to time. > > When I run this and pump indexing data into it, I see index files in the > directory coming in fast and furious but I dont see a segment file. I guess > that is because I dont call close or commit on the IW. My question is what > should I do so that every so often new segments are written? Data is > getting flushed to the disk but there is no Segment info being written. I > must be missing something. > > thanks for all the help guys, > Shouvik --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org