From user-return-10008-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Wed Apr 14 12:30:17 2010 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 10269 invoked from network); 14 Apr 2010 12:30:17 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 14 Apr 2010 12:30:17 -0000 Received: (qmail 69183 invoked by uid 500); 14 Apr 2010 12:30:16 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 69148 invoked by uid 500); 14 Apr 2010 12:30:16 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 69140 invoked by uid 99); 14 Apr 2010 12:30:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Apr 2010 12:30:16 +0000 X-ASF-Spam-Status: No, hits=1.0 required=10.0 tests=AWL,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of manokaran@gmail.com designates 209.85.160.52 as permitted sender) Received: from [209.85.160.52] (HELO mail-pw0-f52.google.com) (209.85.160.52) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Apr 2010 12:30:09 +0000 Received: by pwi1 with SMTP id 1so25282pwi.11 for ; Wed, 14 Apr 2010 05:29:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:content-type; bh=dkzAB3/yU6gwd4ldSV04riIzxd8N8ljMMd/WWNkLyWI=; b=IUP1c4yxOnqFd1Alt9ncdE1ubAnLfPSqB/MDYvPxKjA46rff/Q4T6CvuWC8WsEcYYH VrkDmaDJkx0w7sf82GjTiR8QmYO7V4DP+EFZ6qLCMGNcmoY13HY1gadXieu+praiKjGY VyU2kDv1S2yl1jfM6/EpO+Zl3z07QB6IpGOTo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=H8e8jc5vFeMfF2+cupVwBZBnLMMYlX0Sp4QYmztvuznWTt8n8yMs0ieopnFMpfZhFn acuDTxiAWrwJj/vODMDehS6bwhA5BJ0AHoTPMoqhVuZuFNjjy5taHU5aiSeI3nsy6zpo Sa+OyNX/TbRMOPwZxWYRexnAw0DP3kBxa2je8= MIME-Version: 1.0 Received: by 10.143.158.1 with HTTP; Wed, 14 Apr 2010 05:29:49 -0700 (PDT) In-Reply-To: References: Date: Wed, 14 Apr 2010 17:59:49 +0530 Received: by 10.142.152.34 with SMTP id z34mr3006352wfd.176.1271248189629; Wed, 14 Apr 2010 05:29:49 -0700 (PDT) Message-ID: Subject: Re: couchdb-lucene reindexes when restarted From: Manokaran K To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=000e0cd2e44ac3a50a048431880c --000e0cd2e44ac3a50a048431880c Content-Type: text/plain; charset=ISO-8859-1 On Wed, Apr 14, 2010 at 5:49 PM, Robert Newson wrote: > Ok, I think I understand this now. > > When you start couchdb-lucene on a database for the first time (and > after a restart), it looks at the update_seq of all the Lucene indexes > it has on disk and takes the lowest number of these. It then uses that > in a call to _changes?since=N. > > My suspicion is you have an index that is no longer reachable (because > you've changed your index function at some point). This index won't be > updated, so it's stuck at 27200. > > I've pushed an update that will log (at DEBUG level, so change > log4j.xml temporarily) how the 'since' value is calculated. It would > be very helpful if you could verify my hypothesis. > > You can fix this, if I'm right, by running _cleanup (check the README > for the syntax) which will delete the unreachable index. I need to > make a real fix, though; namely, the update_seq calculation should > ignore unreachable indexes. > > Your hypothesis is likely. A couple of days back, I was getting some doc ids as response to some query but the doc was not available in couchdb. Most likely c-l returned some doc ids that it had indexed earlier but since I drop and recreate the db in couchdb during development, c-l did not know about it! But I was not able to recreate this problem. Will use the latest build and update you. thanks, mano --000e0cd2e44ac3a50a048431880c--