accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2361) droptable created infinite METADATA scan loop
Date Fri, 23 Jan 2015 01:10:34 GMT

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

Christopher Tubbs commented on ACCUMULO-2361:
---------------------------------------------

What is going on with this issue? It's still open, has commits against it, but no updates
in awhile. The version number seems to keep getting bumped. Is this even still an issue? If
no reply, I'm closing it with the fixVersions that [~vines] mentioned (1.5.1 and 1.6.0), because
it seems like it was fixed *at least* by then, if not earlier.

> droptable created infinite METADATA scan loop
> ---------------------------------------------
>
>                 Key: ACCUMULO-2361
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2361
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.5.1
>         Environment: accumulo-1.5.0 with sqrrl extensions.
>            Reporter: Chris McCubbin
>            Priority: Critical
>             Fix For: 1.5.3, 1.7.0, 1.6.3
>
>         Attachments: AccumuloHammerTableCreation.java, AccumuloHammerTableCreation.java,
Screen Shot 2014-02-12 at 2.27.11 PM.png, Screen Shot 2014-02-12 at 2.28.09 PM.png, TableCreationHammerIT.java,
jstack1.txt, jstack2.txt, jstack3.txt, masterJstack.txt, masterJstack2.txt, masterJstack3.txt,
short.debug.log
>
>
> Working with [~vines] on this one...
> Setup: Created a couple tables, added some data, then dropped them. The drop hangs and
!METADATA (which has ~400 entries) is scanned in what looks like an infinite loop.
> The table being dropped loks like this in !METADATA:
> {code}
> root@sqrrl> scan -b 3 -e 5 -t !METADATA
> 4;\x00\x00\x06f srv:dir []    /t-00000b6
> 4;\x00\x00\x06f srv:lock []    tservers/10.10.1.209:9997/zlock-0000000000$144274cd317000b
> 4;\x00\x00\x06f srv:time []    M0
> 4;\x00\x00\x06f ~tab:~pr []    \x00
> 4;\x00\x00\x0C\xCC loc:144274cd3170008 []    10.10.1.107:9997
> 4;\x00\x00\x0C\xCC srv:dir []    /t-00000bj
> 4;\x00\x00\x0C\xCC srv:lock []    tservers/10.10.1.209:9997/zlock-0000000000$144274cd317000b
> 4;\x00\x00\x0C\xCC srv:time []    M0
> 4;\x00\x00\x0C\xCC ~tab:~pr []    \x01\x00\x00\x06f
> 4;\x00\x00\x133 srv:dir []    /t-000002h
> 4;\x00\x00\x133 srv:lock []    tservers/10.10.1.209:9997/zlock-0000000000$144274cd317000b
> 4;\x00\x00\x133 srv:time []    M0
> 4;\x00\x00\x133 ~tab:~pr []    \x01\x00\x00\x0C\xCC
> {code}
> We think this may be the relevant message in the master debug logs:
> {code}
> 2014-02-12 19:13:31,397 [tableOps.CleanUp] DEBUG: Still waiting for table to be deleted:
4 saw inconsistencynull 4;^@^@^L?;^@^@^Ff
> 2014-02-12 19:13:31,459 [tableOps.CleanUp] DEBUG: Still waiting for table to be deleted:
4 saw inconsistencynull 4;^@^@^L?;^@^@^Ff
> 2014-02-12 19:13:31,524 [tableOps.CleanUp] DEBUG: Still waiting for table to be deleted:
4 saw inconsistencynull 4;^@^@^L?;^@^@^Ff
> 2014-02-12 19:13:31,588 [tableOps.CleanUp] DEBUG: Still waiting for table to be deleted:
4 saw inconsistencynull 4;^@^@^L?;^@^@^Ff
> 2014-02-12 19:13:31,662 [tableOps.CleanUp] DEBUG: Still waiting for table to be deleted:
4 saw inconsistencynull 4;^@^@^L?;^@^@^Ff
> 2014-02-12 19:13:31,725 [tableOps.CleanUp] DEBUG: Still waiting for table to be deleted:
4 saw inconsistencynull 4;^@^@^L?;^@^@^Ff
> 2014-02-12 19:13:31,788 [tableOps.CleanUp] DEBUG: Still waiting for table to be deleted:
4 saw inconsistencynull 4;^@^@^L?;^@^@^Ff
> 2014-02-12 19:13:31,854 [tableOps.CleanUp] DEBUG: Still waiting for table to be deleted:
4 saw inconsistencynull 4;^@^@^L?;^@^@^Ff
> 2014-02-12 19:13:31,917 [tableOps.CleanUp] DEBUG: Still waiting for table to be deleted:
4 saw inconsistencynull 4;^@^@^L?;^@^@^Ff
> ...etc
> {code}
> Graceful accumulo reboot hangs. 
> Hard reboot of everything (control-c'd) clears the problem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message