accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-3021) Limit size of split rows
Date Thu, 21 Aug 2014 21:01:11 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Keith Turner updated ACCUMULO-3021:
-----------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> 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
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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