hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-3020) Splitting .META. broke since new master went in
Date Tue, 21 Sep 2010 18:32:35 GMT

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

stack updated HBASE-3020:
-------------------------

    Attachment: 3020.txt

Here's a test that tries to repro the issue.  TRUNK doesn't seem to have the issue reported.
 I then tried killing server hosting .META. on running cluster and it made a listing like
this:

{code}
$ ./bin/hadoop fs -lsr /hbase/.META.
drwxr-xr-x   - stack supergroup          0 2010-09-21 18:28 /hbase/.META./1028785192
drwxr-xr-x   - stack supergroup          0 2010-09-20 17:46 /hbase/.META./1028785192/.oldlogs
-rw-r--r--   3 stack supergroup        124 2010-09-20 17:46 /hbase/.META./1028785192/.oldlogs/hlog.1285004768530
-rw-r--r--   3 stack supergroup        618 2010-09-20 17:46 /hbase/.META./1028785192/.regioninfo
drwxr-xr-x   - stack supergroup          0 2010-09-21 18:25 /hbase/.META./1028785192/info
-rw-r--r--   3 stack supergroup    2584784 2010-09-21 18:25 /hbase/.META./1028785192/info/3297183599923909123
drwxr-xr-x   - stack supergroup          0 2010-09-21 18:28 /hbase/.META./1028785192/recovered.edits
{code}

Which looks right.

> Splitting .META. broke since new master went in
> -----------------------------------------------
>
>                 Key: HBASE-3020
>                 URL: https://issues.apache.org/jira/browse/HBASE-3020
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>            Reporter: stack
>            Assignee: stack
>            Priority: Blocker
>             Fix For: 0.90.0
>
>         Attachments: 3020.txt
>
>
> From Ryan:
> Log recovery didn't seem to run during META open, here is my hadoop lsr:
> {code}
> drwxr-xr-x   - hadoop supergroup          0 2010-09-20 19:20 /hbase-206/.META.
> drwxr-xr-x   - hadoop supergroup          0 2010-09-20 19:20
> /hbase-206/.META./.META.,,1
> drwxr-xr-x   - hadoop supergroup          0 2010-09-20 19:20
> /hbase-206/.META./.META.,,1/recovered.edits
> -rw-r--r--   3 hadoop supergroup      35544 2010-09-20 19:20
> /hbase-206/.META./.META.,,1/recovered.edits/0000000000000000008
> drwxr-xr-x   - hadoop supergroup          0 2010-09-20 13:36
> /hbase-206/.META./1028785192
> drwxr-xr-x   - hadoop supergroup          0 2010-09-20 13:36
> /hbase-206/.META./1028785192/.oldlogs
> -rw-r--r--   3 hadoop supergroup        124 2010-09-20 13:36
> /hbase-206/.META./1028785192/.oldlogs/hlog.1285015016913
> -rw-r--r--   3 hadoop supergroup       1018 2010-09-20 13:36
> /hbase-206/.META./1028785192/.regioninfo
> drwxr-xr-x   - hadoop supergroup          0 2010-09-20 13:36
> /hbase-206/.META./1028785192/historian
> drwxr-xr-x   - hadoop supergroup          0 2010-09-20 13:36
> /hbase-206/.META./1028785192/info
> {code}
> Notice how above recovered.edits is under a dir which is not the encoded name?
> This is my fault I'd guess.  I tried to put in place actual region names of -ROOT- and
.META. rather than the anonymous encodings.  Looks like I broke something split of .META.
when I committed new master.  Will fix in morning.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message