[HBASE-26974] Introduce a LogRollProcedure

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Fix Version/s: 3.0.0-beta-2
• Component/s: backup&restore, proc-v2
• Labels: pull-request-available
• Assignee: ruanhui
• Reporter: ruanhui
• Created: 25/Apr/22 05:21
• Updated: 6 days ago 04:00

Description

The current log-rolling for all regionservers is based in ZK. Here is an attempt to reimplement it with procedure v2.

Here are some requirements about the implementation.
The procedure can be introduced as a new feature. It should remain fully compatible with previous implementations. Also, this feature can be disabled by the configuration. Currently we only use the logroll procedure when taking a backup job, so I think all code logic should be implemented in the hbase-backup module as much as possible(I'm not sure if this is the right way to do it. If you have any suggestions, please let me know).

Here are some details about the implementation.
LogRollProcedure
The LogRollProcedure is used to roll WAL for all the regionservers in the cluster. It acquires the shared lock of the backup system table.
RSLogRollProcedure
The RSLogRollProcedure is used to schedule a RSLogRollRemoteProcedure for each regionserver. When the subprocedure returns, the RSLogRollProcedure will check the logrolling result in the backup system table. If failed, The RSLogRollProcedure will schedule a new RSLogRollRemoteProcedure to retry.
RSLogRollRemoteProcedure
The RSLogRollRemoteProcedure is used to send the log roll request to the remote server.

This is only the first version implementation, any suggestions and feedbacks are appreciated.

Issue Links

• is a child of: HBASE-21488 Reimplement proc-v1 based procedures with proc-v2
• links to: GitHub Pull Request #4367
• links to: GitHub Pull Request #5408