Uh oh!
There was an error while loading. Please reload this page.
HBASE-25445: Use WAL FS instead of master FS in SplitWALManager - #2844
Conversation
dasanjan1296
commented
Jan 5, 2021
- If 'hbase.wal.dir' and 'hbase.rootdir' are configured to different filesystem instances, SplitWALRemoteProcedure archived split WAL failed since SplitWALManager using wrong fs instance. SplitWALManager should use WAL corresponding fs instance.
ramkrish86
left a comment
There was a problem hiding this comment.
Any test case to capture this regression? Else LGTM.
dasanjan1296
commented
Jan 5, 2021
@ramkrish86 I have added some testing details in the corresponding JIRA for reproducing the error. |
Apache-HBase
commented
Jan 5, 2021
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jan 5, 2021
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Jan 5, 2021
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Jan 5, 2021
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Jan 5, 2021
🎊 +1 overall
This message was automatically generated. |
There was a problem hiding this comment.
Please add a UT at TestSplitWALManager for this condition, as already suggested by @ramkrish86 . This is a simple, yet an important fix, we should safeguard SplitWALManager from inadvertent changes that could suppress this fix.
Apache-HBase
commented
Jan 7, 2021
🎊 +1 overall
This message was automatically generated. |
virajjasani
left a comment
There was a problem hiding this comment.
Nice test, just a couple of nits
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
virajjasani
left a comment
There was a problem hiding this comment.
+1, Thanks @dasanjan1296
virajjasani
commented
Jan 7, 2021
Once QA results are in, will merge this PR. |
virajjasani
commented
Jan 7, 2021
I think there seems some problem with Jenkins, the recent build is aborted and I am not able to schedule a new build. |
virajjasani
commented
Jan 7, 2021
New build is triggered |
Apache-HBase
commented
Jan 7, 2021
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Jan 7, 2021
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Jan 7, 2021
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jan 7, 2021
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jan 7, 2021
🎊 +1 overall
This message was automatically generated. |
virajjasani
commented
Jan 7, 2021
Build is taking more time. Let me merge this PR, I have validated test locally and we also have result available here https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2844/5/testReport/org.apache.hadoop.hbase.master/TestSplitWALManager/ |
Signed-off-by: Pankaj <pankajkumar@apache.org> Signed-off-by: ramkrish86 <ramkrishna@apache.org> Signed-off-by: Viraj Jasani <vjasani@apache.org>
Signed-off-by: Pankaj <pankajkumar@apache.org> Signed-off-by: ramkrish86 <ramkrishna@apache.org> Signed-off-by: Viraj Jasani <vjasani@apache.org>
Signed-off-by: Pankaj <pankajkumar@apache.org> Signed-off-by: ramkrish86 <ramkrishna@apache.org> Signed-off-by: Viraj Jasani <vjasani@apache.org>
Signed-off-by: Pankaj <pankajkumar@apache.org> Signed-off-by: ramkrish86 <ramkrishna@apache.org> Signed-off-by: Viraj Jasani <vjasani@apache.org>
Apache-HBase
commented
Jan 7, 2021
🎊 +1 overall
This message was automatically generated. |
wchevreuil
left a comment
There was a problem hiding this comment.
I had some nits regarding the current UT, but since this got merged already, we may follow on another jira.
| @Test | ||
| public void testWALArchiveWithDifferentWalAndRootFS() throws Exception{ | ||
| HBaseTestingUtility test_util_2 = new HBaseTestingUtility(); |
There was a problem hiding this comment.
nit: non static variables should follow camel case style.
| } | ||
| executor.submitProcedure(splitProcedure); | ||
| LOG.info("Submitted SplitProcedure."); | ||
| test_util_2.waitFor(30000, () -> executor.getProcedures().stream() |
There was a problem hiding this comment.
Shouldn't we filter by the split procedure submitted and assert it has completed success?