hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12978) hbase:meta has a row missing hregioninfo and it causes my long-running job to fail
Date Mon, 09 Feb 2015 19:37:34 GMT

    [ https://issues.apache.org/jira/browse/HBASE-12978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14312710#comment-14312710

Devaraj Das commented on HBASE-12978:

[~stack] wondering if this is happening because of the fact that the balancer is doing its
job in the background. Scenario is:
0. The balancer computed a plan for the regions but not executed all the moves yet.
1. The region in question is deleted from the meta (maybe due to a split etc)
2. The balancer does its job and assigns the region to some RS. That RS does a put in the
meta table when it successfully opens the region. That put recreates the meta entry but this
time the hri won't be there...

> hbase:meta has a row missing hregioninfo and it causes my long-running job to fail
> ----------------------------------------------------------------------------------
>                 Key: HBASE-12978
>                 URL: https://issues.apache.org/jira/browse/HBASE-12978
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>             Fix For: 1.0.1
> Testing 1.0.0 trying long-running tests.
> A row in hbase:meta was missing its HRI entry. It caused the job to fail. Around the
time of the first task failure, there are balances of the hbase:meta region and it was on
a server that crashed. I tried to look at what happened around time of our writing hbase:meta
and I ran into another issue; 20 logs of 256MBs filled with WrongRegionException written over
a minute or two. The actual update of hbase:meta was not in the logs, it'd been rotated off.

This message was sent by Atlassian JIRA

View raw message