You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2008/06/06 21:56:45 UTC

[jira] Commented: (HBASE-670) Historian deadlocks if regionserver is at global memory boundary and is hosting .META.

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

stack commented on HBASE-670:
-----------------------------

On IRC, was asking if could add history for .META. itself, probably the table we're most interested in.  My experience over last few days changing historian so it is only enabled after .META. has been deployed and issues like this one have me thinking it'd be hard to do.

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