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 3768F10F4A for ; Mon, 4 Nov 2013 21:34:23 +0000 (UTC) Received: (qmail 63782 invoked by uid 500); 4 Nov 2013 21:34:22 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 63761 invoked by uid 500); 4 Nov 2013 21:34:22 -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 63703 invoked by uid 99); 4 Nov 2013 21:34:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Nov 2013 21:34:22 +0000 Date: Mon, 4 Nov 2013 21:34:22 +0000 (UTC) From: "Mike Matrigali (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (DERBY-6283) indexStat daemon processing tables over and over even when there are no changes in the tables in soft upgraded database. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-6283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali resolved DERBY-6283. ----------------------------------- Resolution: Fixed > indexStat daemon processing tables over and over even when there are no changes in the tables in soft upgraded database. > ------------------------------------------------------------------------------------------------------------------------ > > Key: DERBY-6283 > URL: https://issues.apache.org/jira/browse/DERBY-6283 > Project: Derby > Issue Type: Bug > Components: Store > Affects Versions: 10.8.3.1, 10.9.2.2, 10.10.1.3, 10.11.0.0 > Reporter: Mike Matrigali > Assignee: Mike Matrigali > Priority: Blocker > Labels: derby_triage10_11 > Fix For: 10.8.3.1, 10.9.2.2, 10.10.1.3, 10.11.0.0 > > Attachments: derby-6283.diff > > > The fix for DERBY-5680 currently requires hard upgrade. A soft upgrade database with an orphaned stat row, that can be caused by something like DERBY-5681, will cause DERBY to spin eating up 100% of a cpu and possibly all the disk bandwith of the disk where the database is located. > We should implement a fix that can be applied to soft upgraded databases if at all possible. > In soft upgraded databases we can no use the work around of dropping the statistics as it is not available > to soft upgraded db's with version < 10.9. The only current workaround is to disable background stats > completely. Dropping and recreating the suspect table may also work. -- This message was sent by Atlassian JIRA (v6.1#6144)