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

Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2018/03/01 05:22:00 UTC

[jira] [Assigned] (HBASE-20107) Add a test case for HBASE-14317

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

Ted Yu reassigned HBASE-20107:
------------------------------

    Assignee: Zephyr Guo

> Add a test case for HBASE-14317
> -------------------------------
>
>                 Key: HBASE-20107
>                 URL: https://issues.apache.org/jira/browse/HBASE-20107
>             Project: HBase
>          Issue Type: Test
>          Components: wal
>    Affects Versions: 3.0.0
>            Reporter: Zephyr Guo
>            Assignee: Zephyr Guo
>            Priority: Minor
>             Fix For: 2.0.0-beta-2
>
>         Attachments: HBASE-20107-v1.patch, HBASE-20107-v2.patch
>
>
> RS might get stuck because of  HBASE-14317. I met same problem in my hbase, and HBASE-14317 can solve this problmen very well.
> But I don't get stuck when I run _TestWalLockup.testLockupWhenSyncInMiddleOfZigZagSetup_.
>  We'll never see stuck in this test case, because FailedSyncBeforeLogCloseException will break _zigzagLatch.waitSafePoint(SyncFuture)_. Finally, _zigzagLatch.releaseSafePoint()_ will be call, and _attainSafePoint(long)_ get out stuck.
>  Here, we add a new test case to simulate stuck RS correctly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)