You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2016/07/12 04:26:11 UTC
[jira] [Issue Comment Deleted] (HBASE-16081) Replication
remove_peer gets stuck and blocks WAL rolling
[ https://issues.apache.org/jira/browse/HBASE-16081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Busbey updated HBASE-16081:
--------------------------------
Comment: was deleted
(was: Please set fix version(s))
> 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
> Fix For: 2.0.0, 1.3.0, 1.4.0
>
> 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)