Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
3.0.0-alpha-1, 2.4.0, 2.2.6, 2.3.2
-
None
-
None
Description
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.
Attachments
Issue Links
- is a clone of
-
HBASE-25445 Old WALs archive fails in procedure based WAL split
- Resolved