[
https://issues.apache.org/jira/browse/HBASE-19929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16354328#comment-16354328
]
stack commented on HBASE-19929:
-------------------------------
The hadoop build fails are the thrift schema download issue failing...
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-install-plugin:2.5.2:install (default-install)
on project hbase-thrift: Failed to install metadata
org.apache.hbase:hbase-thrift:3.0.0-SNAPSHOT/maven-metadata.xml: Could not
parse metadata
/home/jenkins/.m2/repository/org/apache/hbase/hbase-thrift/3.0.0-SNAPSHOT/maven-metadata-local.xml:
in epilog non whitespace content is not allowed but got / (position: END_TAG
seen ...</metadata>\n/... @25:2) -> [Help 1]
On the patch, would be sweet if we could do w/o the DrainBarrier. Yes,
circumstances have changed since it was introduced and your observation that it
is frustrated now anyways by the close flag is a good one. Lets try it. One
question up on rb...
> 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)
