accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3021) Limit size of split rows
Date Fri, 25 Jul 2014 23:55:38 GMT

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

Josh Elser commented on ACCUMULO-3021:
--------------------------------------

I'm pretty sure he means the rowId from the Key of the Tablet split. As in, someone did {{addsplits
really_long_row}} or the system happened to chose the split point out of chance from an existing
rowId. This is what is actually stored in the metadata table.

> 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
>             Fix For: 1.7.0
>
>
> 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)

Mime
View raw message