[ https://issues.apache.org/jira/browse/HBASE-25445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17260005#comment-17260005 ]
Viraj Jasani edited comment on HBASE-25445 at 1/6/21, 7:21 PM: --------------------------------------------------------------- FYI [~ndimiduk] [~huaxiangsun] Would you like to wait for some time to get this merged before spinning 2.3.4 RC? We are just waiting for a unit test and it's good to go. was (Author: vjasani): FYI [~ndimiduk] [~huaxiangsun] Would you like to wait for some time to get this merged before spinning 2.3.4 RC? We are just waiting for a test and it's good to go. > 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.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)