hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashish Singhi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14621) ReplicationLogCleaner gets stuck when a regionserver crashes
Date Fri, 16 Oct 2015 07:10:06 GMT

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

Ashish Singhi commented on HBASE-14621:

I could write a test case to simulate this for {{ReplicationHFileCleaner}} which is part of
May be you can also try this for {{ReplicationLogCleaner}},
    ReplicationHFileCleaner cleaner = new ReplicationHFileCleaner();

    ReplicationQueuesClient replicationQueuesClient = Mockito.mock(ReplicationQueuesClient.class);
    Mockito.when(replicationQueuesClient.getHFileRefsNodeChangeVersion()).thenReturn(1, 2);
    Class<? extends ReplicationHFileCleaner> cleanerClass = cleaner.getClass();
    Field rqc = cleanerClass.getDeclaredField("rqc");
    rqc.set(cleaner, replicationQueuesClient);


I have added a 15 second timeout to the test. Without the fix the test will timeout and with
the fix it will pass.
I hope this will help.

> ReplicationLogCleaner gets stuck when a regionserver crashes
> ------------------------------------------------------------
>                 Key: HBASE-14621
>                 URL: https://issues.apache.org/jira/browse/HBASE-14621
>             Project: HBase
>          Issue Type: Bug
>          Components: Replication
>            Reporter: Ashu Pachauri
>            Assignee: Ashu Pachauri
>            Priority: Critical
>         Attachments: HBASE-14621.patch
> The ReplicationLogCleaner has a bug that makes it get stuck in an infinite loop when
a regionserver crashes. This bug was introduced in the fix for HBASE-12865; which makes sure
that the loadWALsFromQueues method attempts a retry whenever the replication node's cversion
is changed in the middle of loading the replication queue for the regionservers. However,
if this scenario actually happens (a regionserver crash in the middle of the operation), it
will get stuck in an infinite loop.
> It has very serious ramifications because the old WALs are not cleaned up because of
this and in a high load environment, the file count in the oldWALs directory soon exceeds
the inode limit and the cluster goes down.

This message was sent by Atlassian JIRA

View raw message