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 zachary.zolton@gmail.com
 designates 209.85.220.228 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=kj1K0lifqJJjiVv4LYrop6HMqrMUZrpzf/jJr5B0plEDUNLY40VzVna7RNnEfz6/SB
         sQbIuKnzVzfTVgXcLjvHZVUc9qnTynODVVR8XjCJjWaIiijq8tdJndRSej6lnWnMJlzu
         UtC6kAvMISqn7HMkmsc1I3vNy1L7zZXj9Cbb8=
MIME-Version: 1.0
In-Reply-To: <f728979f0907101144p5d1903ffqbf3e2ce877c58ad4@mail.gmail.com>
References: <8ffb00ae0906082313j798fe874u3925cfd75de562ac@mail.gmail.com>
	<A591E48D-0CDB-4C4D-9DA9-062B2265D5E7@apache.org>
 <f728979f0907101010p35ea868ewd26ef1cbb7d05449@mail.gmail.com>
	<2F5EA1F1-03E0-4714-AE50-05AA3A70CA05@apache.org>
 <f728979f0907101144p5d1903ffqbf3e2ce877c58ad4@mail.gmail.com>
From: Zachary Zolton <zachary.zolton@gmail.com>
Date: Fri, 10 Jul 2009 13:47:50 -0500
Message-ID: <f728979f0907101147j5cadd7fve921261d462d4b4d@mail.gmail.com>
Subject: Re: Updating views in a production system
To: user@couchdb.apache.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Argh... accidentally hit "send" too soon~!!

Awesome, but since I'm still using 0.9 in production, I'll need to do
something else in the meantime.

Will stale=3Dok queries remain performant during the re-indexing imposed
by pushing an updated design document?

If that's gonna work for me, I'll probably change my deployment
strategy to the following:
  1) flip the "latency" switch on, in a admin page
  2) now all queries use stale=3Dok
  3) push our new design documents
  4) "prime" a view for each design document
  5) somehow know when the indexing has finished
  6) flip the "latency" switch off
  7) now queries should go to the freshly-built indexes!

Does anyone see glaring problems with this approach?

=97ZZ

On Fri, Jul 10, 2009 at 1:44 PM, Zachary Zolton<zachary.zolton@gmail.com> w=
rote:
> Awesome, but since I'm still using 0.9 in production, I'll need to do
> something else in the meantime.
>
> Will stale=3Dok queries remain performant during the re-indexing imposed
> by pushing an updated design document?
>
>
> Does anyone see glaring problems with this approach?
>
>
> Cheers,
>
> Zach
>
>
> On Fri, Jul 10, 2009 at 1:18 PM, Adam Kocoloski<kocolosk@apache.org> wrot=
e:
>> Yep, you got it.
>>
>> Adam
>>
>> On Jul 10, 2009, at 1:10 PM, Zachary Zolton wrote:
>>
>>> This commit would appear to address the situation in 0.10:
>>>
>>>
>>> http://github.com/halorgium/couchdb/commit/d3f40115b0323e0ec66ed2fa08ad=
b9852d548003
>>>
>>>
>>> On Sun, Jun 14, 2009 at 4:58 AM, Jan Lehnardt<jan@apache.org> wrote:
>>>>
>>>> Hi Nadav,
>>>>
>>>> On 9 Jun 2009, at 08:13, Nadav Samet wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Whenever I modify a design document of a view or add a new one, I am
>>>>> query
>>>>> any of the other views. Is it the expected behavior (on 0.10.0a) ?
>>>>
>>>> Yes.
>>>>
>>>>> If so, is it possible to avoid downtime when adding/editing a view on=
 a
>>>>> single replica setup?
>>>>
>>>> Not yet, there's a ticket in JIRA that will remind us to allow for the
>>>> following
>>>> pattern:
>>>>
>>>> Create a new _design/foo2 instead of editing _design/foo. Query
>>>> _design/foo2
>>>> so a new view index is built and then HTTP COPY _design/foo2 to
>>>> _design/foo
>>>> and have CouchDB keep using the pre-created index.
>>>>
>>>> Cheers
>>>> Jan
>>>> --
>>>>
>>>>
>>
>>
>