hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-3660) If regions assignment fails, clients will be directed to stale data from .META.
Date Fri, 18 Mar 2011 03:26:29 GMT

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

stack commented on HBASE-3660:
------------------------------

But the region is not deployed right Cosmin?  And can't if LZO is borked?  Isn't this the
bigger problem?

The .META. will be updated on successful region deploy?  We keep the old .META. data around
because we want to assign regions to their old location on restart (because of locality).

> If regions assignment fails, clients will be directed to stale data from .META.
> -------------------------------------------------------------------------------
>
>                 Key: HBASE-3660
>                 URL: https://issues.apache.org/jira/browse/HBASE-3660
>             Project: HBase
>          Issue Type: Bug
>          Components: master, regionserver
>    Affects Versions: 0.90.1
>            Reporter: Cosmin Lehene
>             Fix For: 0.90.2
>
>
> I've noticed this when the IP on my machine changed (it's even easier to detect when
LZO doesn't work)
> Master loads .META. successfully and then starts assigning regions.
> However LZO doesn't work so HRegionServer can't open the regions. 
> A client attempts to get data from a table so it reads the location from .META. but goes
to a totally different server (the old value in .META.)
> This could happen without the LZO story too. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message