Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of jrhuggins@gmail.com
 designates 209.85.200.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references:x-google-sender-auth;
        b=YNIR6339+D6sBThc0ZPPhKBpLEUx2BjO56MqnyHyGAf5lWr1NeltS5tIwDfM2Rti/2
         uZ8Ti99BHKcVwX+LYB2DdJMDIi493gkW4dKmdCAxsM59+7Yl9K3PJiu7aBcgZJ5QuQXD
         kpMGyR8rB3vSI4ilStotYD5kFuVpXHUYZHedA=
Message-ID: <53b9568a0901190547r4356f8a5u3e439c7eb38c2c40@mail.gmail.com>
Date: Mon, 19 Jan 2009 07:47:22 -0600
From: "Jason Huggins" <jason@jrandolph.com>
Sender: jrhuggins@gmail.com
To: user@couchdb.apache.org
Subject: Re: Is there a way to force a rebuild of an index?
In-Reply-To: <8A67AACF-0D02-4B69-9319-9103143E35FD@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <53b9568a0901190506x34349539h7847565b9d0f866c@mail.gmail.com>
	 <8A67AACF-0D02-4B69-9319-9103143E35FD@apache.org>

On Mon, Jan 19, 2009 at 7:16 AM, Jan Lehnardt <jan@apache.org> wrote:
> Is the new server running 0.8.0 as well?

Yes. they are both running CouchDB 0.8.0.

> Is there a endian-difference
> or a 32bit to 64bit upgrade?

No. They are both 32-bit. More context: I'm moving between EC2
instances. Both are based on 32-bit AMIs from Alestic (This one:
http://developer.amazonwebservices.com/connect/entry.jspa?externalID=1427&categoryID=101
)

> I'm not sure the last two things affect us,
> but that could cause problems). Also: Could "stale" be due to some
> HTTP proxy or browser cache?

I thought the same thing at first. Though I did try ruling out browser
cache by trying multiple times on multiple browsers (and clearing the
cache!). Also I am running everything through an HTTP proxy... but
also viewing the "raw metal" at port 5984 didn't help either.

> Updating indexes can usually be triggered by changing the design doc
> they are defined in and deleting the files should work as well.
>
> It might also be worth upgrading, since a bit of work went into that
> area since 0.8.0.

That's what I was suspecting. Should I try 0.8.1 or go all the way to trunk?

Thanks,
   -j