Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 91BE811199 for ; Wed, 20 Aug 2014 18:52:50 +0000 (UTC) Received: (qmail 95632 invoked by uid 500); 20 Aug 2014 18:52:50 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 95607 invoked by uid 500); 20 Aug 2014 18:52:50 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 95596 invoked by uid 99); 20 Aug 2014 18:52:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Aug 2014 18:52:50 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of m.v.lunteren@gmail.com designates 209.85.192.44 as permitted sender) Received: from [209.85.192.44] (HELO mail-qg0-f44.google.com) (209.85.192.44) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Aug 2014 18:52:45 +0000 Received: by mail-qg0-f44.google.com with SMTP id e89so7919795qgf.3 for ; Wed, 20 Aug 2014 11:52:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=tufCYX0AgZWXdTueHPma1oRNtVnWRiWovFHjhXLKIB8=; b=hBIOu8wbbYC3uaW23tgVouGFD37dZK9WYdRqPsd2Z3h6Zf5FuLGMWZu/tywcYQwEOa RNDajjuZX/PdBCEI3D96ISez/Kwz0LrYZpRvletuJflZWsZf0n5hhSprvXpSyzYJKFtk 4tCauJ2KeeGG0r68HWt14PZJPeUIHQ4knG+8unWKwDGBypVLEMMbxhq9xLAB9whjKhr7 w2UiPoKPgnHuQ1AOE8ixcUJ1gkR8XXKhO1O9Yl6QU+7yGOtxdMyPFsTRcnfAUy0A2H+n SAq4GJeyuLczwb1ldpKILFPvaQHAlFrw1nodSfU2x+2m4EFUD2QmXyAduh78nVSu99Mf XNbQ== MIME-Version: 1.0 X-Received: by 10.140.88.41 with SMTP id s38mr75619494qgd.73.1408560744305; Wed, 20 Aug 2014 11:52:24 -0700 (PDT) Received: by 10.96.37.67 with HTTP; Wed, 20 Aug 2014 11:52:24 -0700 (PDT) In-Reply-To: <53F4E589.9010802@oracle.com> References: <53F4E589.9010802@oracle.com> Date: Wed, 20 Aug 2014 11:52:24 -0700 Message-ID: Subject: Re: testing crash recovery From: Myrna van Lunteren To: derbydev Content-Type: multipart/alternative; boundary=001a11c13e7ecf220f0501141aa8 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c13e7ecf220f0501141aa8 Content-Type: text/plain; charset=UTF-8 Hi, I cannot check on the 10.7 release docs right now, I get 'Service Unavailable' on wiki access, but I suspect I last did anything in this area. As far as I remember, it was a manual approach of loading up some randomly created database, kick off some process (I might have started one of the system tests for this), then crashing the jvm (killing the jvm), and then using ij, check the database (likely I just did some simple operations (create, delete, select, update), and probably consistency checker). Unless someone knows another approach that was done under this heading... Myrna On Wed, Aug 20, 2014 at 11:14 AM, Rick Hillegas wrote: > I would like to understand what additional testing of the release > candidate should be performed in order to satisfy the checklist item called > "Recovery after crashing engine". Various recovery tests are run as part of > our platform release tests, but it I don't see any tests for crash recovery. > > We do have a crash recovery test for encrypted databases > (CryptoCrashRecovery), but that only runs on debug jars. So it has only > been exercised by nightly/continuousIntegration tests on the 10.11 branch, > not on the release candidate itself. > > I have some questions for the Store experts: > > 1) Does "Recovery after crashing engine" mean running CryptoCrashRecovery > on the debug distribution of 10.11.1.1? > > 2) Does it entail some other, formal tests? > > 3) Or is it meant to cover some other ad-hoc tests which are run by hand > and are not checked in under subversion? > > Thanks, > -Rick > --001a11c13e7ecf220f0501141aa8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

I cannot check on the 10.7 release docs ri= ght now, I get 'Service Unavailable' on wiki access, but I suspect = I last did anything in this area. As far as I remember, it was a manual app= roach of loading up some randomly created database, kick off some process (= I might have started one of the system tests for this), then crashing the j= vm (killing the jvm), and then using ij, check the database (likely I just = did some simple operations (create, delete, select, update), and probably c= onsistency checker).

Unless someone knows another approach that was done under th= is heading...

Myrna


On Wed, Aug 20, 2014 at 11:14 AM, Rick= Hillegas <rick.hillegas@oracle.com> wrote:
I would like to understand what additional t= esting of the release candidate should be performed in order to satisfy the= checklist item called "Recovery after crashing engine". Various = recovery tests are run as part of our platform release tests, but it I don&= #39;t see any tests for crash recovery.

We do have a crash recovery test for encrypted databases (CryptoCrashRecove= ry), but that only runs on debug jars. So it has only been exercised by nig= htly/continuousIntegration tests on the 10.11 branch, not on the release ca= ndidate itself.

I have some questions for the Store experts:

1) Does "Recovery after crashing engine" mean running CryptoCrash= Recovery on the debug distribution of 10.11.1.1?

2) Does it entail some other, formal tests?

3) Or is it meant to cover some other ad-hoc tests which are run by hand an= d are not checked in under subversion?

Thanks,
-Rick

--001a11c13e7ecf220f0501141aa8--