Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of will.heger@gmail.com designates
 209.85.214.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAHGcXegGstnpuSy9agvfZf2XO8HVzxXwiRxkXtVt7kQ2=oUvHA@mail.gmail.com>
References: 
 <CAHGcXeiH-TbzBMGvhRHWFsd7fNx0TXRjuuA-keDZ=55N4qMH1g@mail.gmail.com>
	<CAHGcXeio36-72sECLp+TUZueAXKJwOUmhiBPOZ9uEU0xa4R_PQ@mail.gmail.com>
	<9ED9A116-1C4B-4BA2-A122-DFF4646E03AF@apache.org>
	<CAHGcXegGstnpuSy9agvfZf2XO8HVzxXwiRxkXtVt7kQ2=oUvHA@mail.gmail.com>
Date: Thu, 16 Aug 2012 02:26:27 -0400
Message-ID: 
 <CAHGcXegx5NdGchUtehUZ-DLV8M7TA0V51XUujuTKr5km30rRkw@mail.gmail.com>
Subject: Re: JavaScript 1.8.5 and Upgrades
From: Will Heger <will.heger@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

So, I pulled a couchjs I had built on a similar machine (distro and
architecture) and the reduce worked, the 1.8.5 Date() behaved
correctly.

But sadly, I ran the test suite and it produced all kinds of crazy
failures, more than I'm comfortable ignoring.

So I think a full upgrade is recommended.  Is this guy's process accurate?
http://blog.cliffano.com/2010/09/10/couchdb-upgrade-from-0-11-0-to-1-0-1/

Is there an official page on the couchdb upgrade process?

Thanks and best regards,
-Will


On Wed, Aug 15, 2012 at 3:56 PM, Will Heger <will.heger@gmail.com> wrote:
> I'm going to try this tonight when I can take the DB offline and
> report back because the results may be interesting.
>
> This was exactly the piece of terrible advice I was looking for!
>
> Thanks Adam,
> -Will
>
>
> On Wed, Aug 15, 2012 at 3:38 PM, Adam Kocoloski <kocolosk@apache.org> wro=
te:
>> On Aug 15, 2012, at 9:32 AM, Will Heger wrote:
>>
>>> After pushing some UTC Date() containing reduce code to a server, I
>>> discovered that the server was using 1.8.0 SpiderMonkey rather than
>>> 1.8.5, balls!
>>>
>>> So, my impression from the docs is that CouchDB needs to be compiled
>>> with a JavaScript engine, there is no swapping up to 1.8.5 from 1.8.0
>>> (but please correct this if I'm wrong, I'd much rather swap the engine
>>> than rebuild a running couchdb).
>>>
>>> So here's my question: What is the a typical or best practice for
>>> performing an upgrade to CouchDb?   Luckily, the server isn't a 24/7
>>> instance, so I have some time to take it down.  But is it:
>>>
>>> 0. doubtful, but is there a way to ugrade the SpiderMonkey in situ?
>>> 1. Is there a upgrade process or 'upgrader' in couchdb somewhere?
>>> 2. If not, do I backup replicate, stop, and build, and "make install"
>>> overtop? Or...
>>> 3. Is it option 2, but I need to eradicate the existing installation,
>>> and if so, how does one eradicate completely couchdb (one installed
>>> from source, IIRC)?
>>>
>>> Apologies in advance if these are answered through Googling, but I
>>> didn't find a succinct explanation.
>>>
>>> And thanks in advance for any assistance.
>>>
>>> Best regards,
>>> -Will
>>
>> Hi Will, if you were so inclined you could install SM185, drop in a new =
couchjs binary that links against it, do a killall to knock out any running=
 couchjs processes, and the server should start using your new build of cou=
chjs for all new requests.  The core database isn't linked to SpiderMonkey =
in any way.  You'll lose any requests that were using a JS process (_show/_=
list/_update, blocking on a _view build, etc.), but that's about it.
>>
>> I probably made a hundred sysadmins spill their coffee just now, but I t=
hought I'd throw it out there anyway.  Cheers,
>>
>> Adam