You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Anjan Das (Jira)" <ji...@apache.org> on 2021/01/05 04:39:00 UTC
[jira] [Updated] (HBASE-25445) SplitWALRemoteProcedure failed to
archive split WAL
[ https://issues.apache.org/jira/browse/HBASE-25445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anjan Das updated HBASE-25445:
------------------------------
Attachment: ServerCrashWrongFSError.png
> 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.2.3, 2.4.1
> Reporter: mokai
> Assignee: Anjan Das
> Priority: Critical
> 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)