[
https://issues.apache.org/jira/browse/HBASE-26974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18020077#comment-18020077
]
Hudson commented on HBASE-26974:
--------------------------------
Results for branch branch-3
[build #465 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/465/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/465/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/465/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk17 hadoop 3.3.5 backward compatibility checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/465/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk17 hadoop 3.3.6 backward compatibility checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/465/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk17 hadoop 3.4.0 backward compatibility checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/465/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test for 3.3.5 {color}
(/) {color:green}+1 client integration test for 3.3.6 {color}
(/) {color:green}+1 client integration test for 3.4.0 {color}
(/) {color:green}+1 client integration test for 3.4.1 {color}
> Introduce a LogRollProcedure
> ----------------------------
>
> Key: HBASE-26974
> URL: https://issues.apache.org/jira/browse/HBASE-26974
> Project: HBase
> Issue Type: Improvement
> Components: backup&restore, proc-v2
> Reporter: ruanhui
> Assignee: ruanhui
> Priority: Minor
> Labels: pull-request-available
> Fix For: 3.0.0-beta-2
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
