Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 26 Feb 2014 22:12:22 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12696704.1393036403067.112662.1393452742611@arcas>
In-Reply-To: <JIRA.12696704.1393036403067@arcas>
References: <JIRA.12696704.1393036403067@arcas>
Subject: [jira] [Commented] (HBASE-10591) Sanity check table configuration
 in createTable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-10591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13913598#comment-13913598 ] 

stack commented on HBASE-10591:
-------------------------------

I +1'd it [~enis]

> Sanity check table configuration in createTable
> -----------------------------------------------
>
>                 Key: HBASE-10591
>                 URL: https://issues.apache.org/jira/browse/HBASE-10591
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>             Fix For: 0.99.0
>
>         Attachments: hbase-10591_v1.patch, hbase-10591_v2.patch, hbase-10591_v3.patch, hbase-10591_v4.patch, hbase-10591_v5.patch
>
>
> We had a cluster completely become unoperational, because a couple of table was erroneously created with MAX_FILESIZE set to 4K, which resulted in 180K regions in a short interval, and bringing the master down due to  HBASE-4246.
> We can do some sanity checking in master.createTable() and reject the requests. We already check the compression there, so it seems a good place. Alter table should also check for this as well.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)