accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Newton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2730) assigned tablets in DELETING state are not deleted
Date Thu, 24 Apr 2014 19:37:15 GMT

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

Eric Newton commented on ACCUMULO-2730:
---------------------------------------

Work-around:  after attempting to delete the table, kill the tablet server to which the tablet
has been defined.

This is how you find out which tablet server has been assigned the problem tablet:

{noformat}
scan -t !METADATA -c future
4;!0< future:14589f3e1de0035 []    10.0.0.1:9997
{noformat}




> assigned tablets in DELETING state are not deleted
> --------------------------------------------------
>
>                 Key: ACCUMULO-2730
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2730
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.5, 1.5.0, 1.5.1, 1.6.0
>         Environment: production "test" environment
>            Reporter: Eric Newton
>            Assignee: Eric Newton
>            Priority: Minor
>             Fix For: 1.6.0
>
>
> A user created a tablet that would not load (made a clone of the !METADATA table in accumulo-1.4.4).
 After realizing that it would never load, he attempted to delete the table.  However, the
master ignores the table state when a tablet is in the assigned state.  Since the tablet never
moved from assigned to hosted, balancing stopped, which eventually caused havoc on the system.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message