[
https://issues.apache.org/jira/browse/HBASE-16081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372109#comment-15372109
]
Hudson commented on HBASE-16081:
--------------------------------
SUCCESS: Integrated in HBase-1.3-IT #750 (See
[https://builds.apache.org/job/HBase-1.3-IT/750/])
HBASE-16081 Wait for Replication Tasks to complete before killing the (antonov:
rev 0fda2bc9e7cbd58d4e67d0e9dcc420bc7ea98eab)
*
hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSourceManager.java
*
hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/HBaseInterClusterReplicationEndpoint.java
*
hbase-server/src/main/java/org/apache/hadoop/hbase/replication/ReplicationEndpoint.java
> Replication remove_peer gets stuck and blocks WAL rolling
> ---------------------------------------------------------
>
> Key: HBASE-16081
> URL: https://issues.apache.org/jira/browse/HBASE-16081
> Project: HBase
> Issue Type: Bug
> Components: regionserver, Replication
> Affects Versions: 1.3.0
> Reporter: Ashu Pachauri
> Assignee: Joseph
> Priority: Blocker
> Attachments: HBASE-16081-v2.patch, HBASE-16081-v3.patch,
> HBASE-16081-v4.patch, HBASE-16081-v5.patch, HBASE-16081-v6.patch,
> HBASE-16081.patch
>
>
> We use a blocking take from CompletionService in
> HBaseInterClusterReplicationEndpoint. When we remove a peer, we try to shut
> down all threads gracefully. But, under certain race condition, the
> underlying executor gets shutdown and the CompletionService#take will block
> forever, which means the remove_peer call will never gracefully finish.
> Since ReplicationSourceManager#removePeer and
> ReplicationSourceManager#recordLog lock on the same object, we are not able
> to roll WALs in such a situation and will end up with gigantic WALs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
