[
https://issues.apache.org/jira/browse/HBASE-25445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17258685#comment-17258685
]
Viraj Jasani commented on HBASE-25445:
--------------------------------------
[~mokai87] To avoid misunderstanding, we should assign Jira to ourself when we
start working on it even if it is going to take more time coming up with PR.
The longer we keep Jira unassigned, more contributors will assume that no one
is working on Jira as of now and hence they can assign it to themselves. Once
you assign Jira to yourself, no one will try to reassign Jira to them without
your formal permission on Jira :)
Thanks for filing this nice Jira!
> 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)
