Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 82D5C1164C for ; Thu, 21 Aug 2014 19:47:12 +0000 (UTC) Received: (qmail 88647 invoked by uid 500); 21 Aug 2014 19:47:12 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 88609 invoked by uid 500); 21 Aug 2014 19:47:12 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 88587 invoked by uid 99); 21 Aug 2014 19:47:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Aug 2014 19:47:12 +0000 Date: Thu, 21 Aug 2014 19:47:12 +0000 (UTC) From: "Jenna Huston (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ACCUMULO-3021) Limit size of split rows 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/ACCUMULO-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jenna Huston updated ACCUMULO-3021: ----------------------------------- Attachment: 0001-ACCUMULO-3021-Added-constraint-for-max-size-of-end-r.patch > Limit size of split rows > ------------------------ > > Key: ACCUMULO-3021 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3021 > Project: Accumulo > Issue Type: Improvement > Affects Versions: 1.4.0 > Reporter: Keith Turner > Assignee: Jenna Huston > Fix For: 1.7.0 > > Attachments: 0001-ACCUMULO-3021-Added-constraint-for-max-size-of-end-r.patch > > > Just ran into an issue where a very large split row was added to Accumulo. The large split row caused the metadata table to split and was pushed up into the root tablet. This caused the root tablet to become unresponsive as many clients and tservers tried to scan the root tablet. Had to write a custom utility for 1.4 to fix this. > I am curious if 1.5 would have been able to merge it away. Even if 1.5 could merge it away, the root tablet becoming unresponsive was really bad. It took a lot of poking and proding to get the system to anything. It would be best to avoid this situation altogether. > Could make the max split size configurable. This config would be used to limit automatic and user added splits. -- This message was sent by Atlassian JIRA (v6.2#6252)