Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1081)
Subject: Re: Data loss
From: Jan Lehnardt <jan@apache.org>
In-Reply-To: <F1CB7B85-2BC0-462D-A189-0B8AD99F05D8@gmail.com>
Date: Sun, 8 Aug 2010 21:06:25 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <80E9C29B-4DE2-4159-B272-AB8BC30BFCD6@apache.org>
References: <AANLkTiku23xASr7UJZ2LQDSFwCbNH5gh5gZuUp8rZpT2@mail.gmail.com>
 <AANLkTinkeDKMQD3tcC0mi7LYKZr5589KDLTtqSaOF2v4@mail.gmail.com>
 <770C713F-BBA2-4E0C-B9BE-9441A053BCA4@apache.org>
 <AEC2839B-3A89-49C8-928C-D0D773D216B1@geek-it.de>
 <7C48F227-12CA-477E-9581-8E87EE4C1610@apache.org>
 <5A99E2CB-F53E-4435-8225-578946239068@apache.org>
 <AANLkTi==UuLebS1usBbyYe5v5xZea5Bn+YwEY4D+riuL@mail.gmail.com>
 <AANLkTinhd8koektKPxOzTQYXQkDnX6rtqwwB++41VWtv@mail.gmail.com>
 <E7016A59-CF52-4E29-A5BA-3100473F8FDF@apache.org>
 <AANLkTikDvN4wvC5Kh1P2-ufPWg=_B0WA-0zYV9YgTGBx@mail.gmail.com>
 <22319C7F-909D-47AD-94E3-F8C9C3369A9F@apache.org>
 <47434ED7-7E89-46E9-BF74-F4F9DFBF43AD@apache.org>
 <5711F16A-A8BB-499A-8DBA-AA02AF6E0BDC@apache.org>
 <C108FB0A-99A5-4249-A515-8BB14C39229F@apache.org>
 <874784AD-0EFB-4E9B-AAB9-D265B2D06D8F@apache.org>
 <AANLkTik03NmsWfFdCQuvmX9hD=5sH6+gT-HeQdypbkNS@mail.gmail.com>
 <36AA1959-96D2-42CF-8342-D7CD5D65206E@apache.org>
 <62675B53-F969-47BA-8E48-2C6983536991@apache.org>
  <3C6...
To: dev@couchdb.apache.org


On 8 Aug 2010, at 18:37, J Chris Anderson wrote:

> Devs,
>=20
> I have started a document which we will use when announcing the bug. I =
plan to move the document from this wiki location to the =
http://couchdb.apache.org site before the end of the day. Please review =
and edit the document before then.
>=20
> http://wiki.couchone.com/page/post-mortem
>=20
> I have a section called "The Bug" which needs a technical description =
of the error and the fix. I'm hoping Adam or Randall can write this, as =
they are most familiar with the issues.
>=20
> Once it is ready, we should do our best to make sure our users get a =
chance to read it.

I made a few more minor adjustments (see page history when you are =
logged in) and have nothing more to add myself, but I'd appreciate if =
Adam or Randall could add a few more tech bits.

--

In the meantime, I've put up a BIG FAT WARNING on the CouchDB downloads =
page: =20

  http://couchdb.apache.org/downloads.html

I plan to update the warning with a link to the post-mortem once that is =
done.

--

Thanks everybody for being on top of this!

Cheers
Jan
--=20


>=20
> Thanks,
> Chris
>=20
> On Aug 8, 2010, at 5:16 AM, Robert Newson wrote:
>=20
>> That was also Adam's conclusion (data loss bug confined to 1.0.0).
>>=20
>> B.
>>=20
>> On Sun, Aug 8, 2010 at 1:10 PM, Jan Lehnardt <jan@apache.org> wrote:
>>>=20
>>> On 8 Aug 2010, at 13:48, Noah Slater wrote:
>>>=20
>>>> Do we need to abort 0.11.2 as well?
>>>=20
>>> 0.11.x does not have this commit as far as I can see.
>>>=20
>>> Cheers
>>> Jan
>>> --
>>>=20
>>>>=20
>>>> On 8 Aug 2010, at 11:45, Jan Lehnardt wrote:
>>>>=20
>>>>>=20
>>>>> On 8 Aug 2010, at 06:35, J Chris Anderson wrote:
>>>>>=20
>>>>>>=20
>>>>>> On Aug 7, 2010, at 8:45 PM, Dave Cottlehuber wrote:
>>>>>>=20
>>>>>>> is this serious enough to justify pulling current 1.0.0 release
>>>>>>> binaries to avoid further installs putting data at risk?
>>>>>>>=20
>>>>>>=20
>>>>>> I'm not sure what Apache policy is about altering a release after =
the fact. It's probably up to use to decide what to do.
>>>>>=20
>>>>> Altering releases are a no-no. The only real procedure is to =
release a new version and deprecate the old one, while optionally =
keeping it around for posterity.
>>>>>=20
>>>>>=20
>>>>>> Probably as soon as 1.0.1 is available we should pull the 1.0.0 =
release off of the downloads page, etc.
>>>>>=20
>>>>> +1.
>>>>>=20
>>>>>> I also think we should do a post-mortem blog post announcing the =
issue and the remedy, as well as digging into how we can prevent this =
sort of thing in the future.
>>>>>>=20
>>>>>> We should make an official announcement before the end of the =
weekend, with very clear steps to remedy it. (Eg: config delayed_commits =
to false *without restarting the server* etc)
>>>>>=20
>>>>> I think so, too.
>>>>>=20
>>>>> Cheers
>>>>> Jan
>>>>> --
>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>> On 8 August 2010 15:08, Randall Leeds <randall.leeds@gmail.com> =
wrote:
>>>>>>>> Yes. Adam already back ported it.
>>>>>>>>=20
>>>>>>>> Sent from my interstellar unicorn.
>>>>>>>>=20
>>>>>>>> On Aug 7, 2010 8:03 PM, "Noah Slater" <nslater@apache.org> =
wrote:
>>>>>>>>=20
>>>>>>>> Time to abort the vote then?
>>>>>>>>=20
>>>>>>>> I'd like to get this fix into 1.0.1 if possible.
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> On 8 Aug 2010, at 02:28, Damien Katz wrote:
>>>>>>>>=20
>>>>>>>>> Thanks.
>>>>>>>>>=20
>>>>>>>>> Anyone up to create a repair tool for w...
>>>>>>>>=20
>>>>>>=20
>>>>>=20
>>>>=20
>>>=20
>>>=20
>=20