[
https://issues.apache.org/jira/browse/HBASE-19929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16354830#comment-16354830
]
stack commented on HBASE-19929:
-------------------------------
Replied on RB. I'm game for trying it. We've gotten good at figuring problems
in shutdown and startup in recent weeks. We should be able to figure quickly if
this DrainBarrier removal a mistake (it looks like a nice cleanup of a vestige
left over from another time when the context was very different). Thanks.
> 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
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 2.0.0-beta-2
>
> 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)
