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-670) Historian deadlocks if regionserver is at global memory boundary and is hosting .META.
Date Fri, 06 Jun 2008 19:54:45 GMT

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

stack resolved HBASE-670.
-------------------------

    Resolution: Fixed

Committed.

> Historian deadlocks if regionserver is at global memory boundary and is hosting .META.
> --------------------------------------------------------------------------------------
>
>                 Key: HBASE-670
>                 URL: https://issues.apache.org/jira/browse/HBASE-670
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>             Fix For: 0.2.0
>
>         Attachments: 670.patch
>
>
> The global memory unit test was deadlocking because historian was trying to update .META.
with flush info -- only the single regionserver was the one hosting the .META. and the regionserver
global lock was in place while memory is full

-- 
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