[
https://issues.apache.org/jira/browse/HBASE-25445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated HBASE-25445:
---------------------------------
Fix Version/s: 2.3.5
2.4.1
2.5.0
2.2.7
3.0.0-alpha-1
> SplitWALRemoteProcedure failed to archive split WAL
> ---------------------------------------------------
>
> 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.5.0, 2.4.1, 2.3.5
>
> 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)
