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

Posted to issues@hbase.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2018/08/01 06:22:40 UTC

[jira] [Issue Comment Deleted] (HBASE-19929) Call RS.stop on a session expired RS may hang

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

Gavin updated HBASE-19929:
--------------------------
    Comment: was deleted

(was: A comment with security level 'jira-users' was removed.)

> Call RS.stop on a session expired RS may hang
> ---------------------------------------------
>
>                 Key: HBASE-19929
>                 URL: https://issues.apache.org/jira/browse/HBASE-19929
>             Project: HBase
>          Issue Type: Bug
>          Components: wal
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 2.0.0-beta-2, 2.0.0
>
>         Attachments: HBASE-19929-v1.patch, HBASE-19929.patch
>
>
> See the discussion in HBASE-19927. The problem is that, for a normal stop we will try to close all the regions and wait until they are all closed. But if the RS has already session expired, master will start the failover work which will move the WAL directory, and then we will be stuck in writing flush marker.



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