incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noah Slater <nsla...@apache.org>
Subject Re: Updating CouchDB installation
Date Thu, 28 Feb 2013 23:15:33 GMT
Which should be merged soon... So, good and bad news, I guess. :)


On 28 February 2013 22:13, Robert Newson <rnewson@apache.org> wrote:

> couchdb can't be hot upgraded, sadly. It's something both Cloudant and
> Benoit have added in their respective forks.
>
> B.
>
> On 28 February 2013 20:57, Noah Slater <nslater@apache.org> wrote:
> > I guess nobody has any pre-cooked ideas. This should hopefully go away
> once
> > we move to a rebar mode. Benoit, am I right? We should be able to upgrade
> > CouchDB instances in-place.
> >
> > Bob, do you have any ideas how do do this as it stands?
> >
> > I guess you could start up a second instance of CouchDB, and do a
> > swap-over. Depending on your system, there could be a number of ways
> > you accomplish that.
> >
> >
> > On 18 February 2013 02:54, Stanley Iriele <siriele2x3@gmail.com> wrote:
> >
> >> Hello,
> >>
> >> This may be a bit of a strange question...how do you update your couchDB
> >> instance?
> >>
> >> I installed mine using the Githup readme and rake. I am on Ubuntu 12.04
> and
> >> i have an instance in production that was bitten by this bug
> >>
> >> https://issues.apache.org/jira/browse/COUCHDB-1651
> >>
> >> It was nice to see this get resolved and it explained a little of what
> goes
> >> on underneath the hood but is there anyway to just update and
> restart?...I
> >> dont think i can take this instance out of production
> >>
> >> To anyone who knows...thanks
> >>
> >> Stanley
> >>
> >
> >
> >
> > --
> > NS
>



-- 
NS

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message