Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <6232874.152561287100053335.JavaMail.jira@thor>
Date: Thu, 14 Oct 2010 19:47:33 -0400 (EDT)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Subject: [jira] Commented: (HBASE-3044) [replication] ReplicationSource
 won't cleanup logs if there's nothing to replicate
In-Reply-To: <10594515.435421285645969817.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-3044:
------------------------------

+1

> [replication] ReplicationSource won't cleanup logs if there's nothing to replicate
> ----------------------------------------------------------------------------------
>
>                 Key: HBASE-3044
>                 URL: https://issues.apache.org/jira/browse/HBASE-3044
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.89.20100924
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.90.0
>
>         Attachments: HBASE-3044.patch
>
>
> ReplicationSource only calls ReplicationSourceManager.logPositionAndCleanOldLogs if it replicated something, meaning that a region server that doesn't host a region with replicable edits will read through the logs but never report the position in zookeeper and won't clean the processed hlogs. This happened on one cluster here and shutting down a region server took a few minutes just to delete all the znodes.

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