Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1543229567.1212781125074.JavaMail.jira@brutus>
Date: Fri, 6 Jun 2008 12:38:45 -0700 (PDT)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Updated: (HBASE-670) Historian deadlocks if regionserver is
 at global memory boundary and is hosting .META.
In-Reply-To: <773667039.1212780885085.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack updated HBASE-670:
------------------------

    Attachment: 670.patch

Disable flush and compaction logging by historian.  Also added logging of onlining and offlining of the historian.

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