[
https://issues.apache.org/jira/browse/HBASE-28037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17759861#comment-17759861
]
Xiaolin Ha commented on HBASE-28037:
------------------------------------
Seems brings by HBASE-25596, we should stop the source reader when it is a
recovered queue and is empty.
> Replication stuck after switching to new WAL but the queue is empty
> -------------------------------------------------------------------
>
> Key: HBASE-28037
> URL: https://issues.apache.org/jira/browse/HBASE-28037
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Affects Versions: 3.0.0-alpha-4, 2.5.5
> Reporter: Xiaolin Ha
> Priority: Major
>
> When the speed of consuming replication WALs is high, and there are something
> wrong when creating new WAL, the swith of replcation source reader to new WAL
> in the queue may happen before the new WAL is created, then the replcation
> will stuck since it can not consume the new WALs soon afterwards anymore.
> Restarting the RS that replication stucking can make the replication recover.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
