You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2010/09/28 05:52:49 UTC

[jira] Created: (HBASE-3044) [replication] ReplicationSource won't cleanup logs if there's nothing to replicate

[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


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.


[jira] Updated: (HBASE-3044) [replication] ReplicationSource won't cleanup logs if there's nothing to replicate

Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Daniel Cryans updated HBASE-3044:
--------------------------------------

    Attachment: HBASE-3044.patch

Fixes the issue and adds a safeguard later on in the code.

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


[jira] Commented: (HBASE-3044) [replication] ReplicationSource won't cleanup logs if there's nothing to replicate

Posted by "stack (JIRA)" <ji...@apache.org>.
    [ 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.


[jira] Resolved: (HBASE-3044) [replication] ReplicationSource won't cleanup logs if there's nothing to replicate

Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Daniel Cryans resolved HBASE-3044.
---------------------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]

Committed to trunk.

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