[HBASE-28037] Replication stuck after switching to new WAL but the queue is empty

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha-4, 2.5.5
• Fix Version/s: 2.4.18, 2.5.6
• Component/s: Replication
• Assignee: Xiaolin Ha
• Reporter: Xiaolin Ha
• Created: 22/Aug/23 01:13
• Updated: 28/Sep/23 21:11
• Resolved: 28/Sep/23 01:07

Description

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.

 

 

Issue Links

• relates to: HBASE-28114 Add more comments to explain why replication log queue could never be empty for normal replication queue
• links to: GitHub Pull Request #5375