[
https://issues.apache.org/jira/browse/HBASE-25445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17260810#comment-17260810
]
Hudson commented on HBASE-25445:
--------------------------------
Results for branch branch-2.3
[build #141 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/141/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/141/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/141/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/141/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/141/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Old WALs archive fails in procedure based WAL split
> ---------------------------------------------------
>
> Key: HBASE-25445
> URL: https://issues.apache.org/jira/browse/HBASE-25445
> Project: HBase
> Issue Type: Bug
> Components: wal
> Affects Versions: 3.0.0-alpha-1, 2.4.0, 2.2.6, 2.3.2
> Reporter: mokai
> Assignee: Anjan Das
> Priority: Critical
> Fix For: 3.0.0-alpha-1, 2.2.7, 2.3.4, 2.5.0, 2.4.1
>
> Attachments: ServerCrashWrongFSError.png
>
>
> If 'hbase.wal.dir' and 'hbase.rootdir' are configured to different
> filesystem, SplitWALRemoteProcedure archived split WAL failed since
> SplitWALManager using wrong fs instance. SplitWALManager should use WAL
> corresponding fs instance.
> Steps to Reproduce:
> * Configure 'hbase.wal.dir' and 'hbase.rootdir' so that they point to
> different fs instances.
> * Start HBase with multiple RS.
> * Create a couple of tables and some rows in them so that the RSs get
> assigned with some regions.
> * Take any RS with non-zero number of regions offline.
> * Check master logs for "Wrong FS" error as shown in the screenshot
> attached.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
