Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E0123FB11 for ; Tue, 2 Apr 2013 01:09:16 +0000 (UTC) Received: (qmail 80294 invoked by uid 500); 2 Apr 2013 01:09:16 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 80219 invoked by uid 500); 2 Apr 2013 01:09:15 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 79943 invoked by uid 99); 2 Apr 2013 01:09:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Apr 2013 01:09:15 +0000 Date: Tue, 2 Apr 2013 01:09:15 +0000 (UTC) From: "Sergey Shelukhin (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-8239) ChaosMonkey actions for root and meta don't work MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Sergey Shelukhin created HBASE-8239: --------------------------------------- Summary: ChaosMonkey actions for root and meta don't work Key: HBASE-8239 URL: https://issues.apache.org/jira/browse/HBASE-8239 Project: HBase Issue Type: Bug Components: test Reporter: Sergey Shelukhin Priority: Minor 1) Meta action doesn't work, it always fails to find the server holding meta, which has been the case for some time now. 2) Root action is no longer relevant: 13/04/01 20:36:25 INFO util.ChaosMonkey: Performing action: Restart region server holding ROOT org.apache.hadoop.hbase.exceptions.TableNotFoundException: Cannot find row in .META. for table: -ROOT-, row=-ROOT-,,99999999999999 at org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:164) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira