hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HBASE-490) Doubly-assigned .META.; master uses one and clients another
Date Tue, 04 Mar 2008 19:35:40 GMT

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

stack resolved HBASE-490.

    Resolution: Fixed

Committed to branch and TRUNK

> Doubly-assigned .META.; master uses one and clients another
> -----------------------------------------------------------
>                 Key: HBASE-490
>                 URL: https://issues.apache.org/jira/browse/HBASE-490
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.1.0, 0.2.0
>            Reporter: stack
>            Priority: Blocker
>             Fix For: 0.1.0, 0.2.0
>         Attachments: 490-0.1-v2.patch, 490-0.16.0.patch, 490-TRUNK-v2.patch, 490-trunk.patch,
> Internal cluster has two .META.,,1 regions up (Its possible for a region to be added
twice to the unassigned map if meta scans run close together).  Worse is that the master is
working with one .META. but when clients come in, they're being give the other.  Makes for
odd results.
> Made it a blocker.  Still trying to track down how master doesn't see subsequent update
of .META. info in -ROOT-.....

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

View raw message