-
Notifications
You must be signed in to change notification settings - Fork 3.4k
HBASE-27775 Use a separate WAL provider for hbase:replication table #5157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HBASE-27775 Use a separate WAL provider for hbase:replication table #5157
Conversation
This is for fixing the TestMultiSlaveReplication, and also to avoid generating a lot of useless data in hbase:replication table, while nothing written to the cluster. The current implementation may still not enough as we may still track the WAL file for hbase:replication, but anyway it will not mess up the normal WAL files. Will dig more and report back here. |
🎊 +1 overall
This message was automatically generated. |
OK, confirmed, there is no problem. We will add a WALActionListener in Replication for tracking the WAL files which need to be replicated, and it will only add the listener to user space WALProvider, so we are safe here. |
🎊 +1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
ba5488b
to
f78fe59
Compare
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
@Apache9 sir. |
hbase-server/src/main/java/org/apache/hadoop/hbase/wal/LazyInitializedWALProvider.java
Show resolved
Hide resolved
I think we could add a UT to confirm that we write the WAL for hbase:replication to a separated file. |
Done. @2005hithlj PTAL. Thanks. |
🎊 +1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
@Apache9 sir LTGM. |
Let me check the test logs for the failed UT. |
Posted the findings on HBASE-27277, TestRaceBetweenSCPAndTRSP is known to be flaky for a while, only in pre commit, anyway. Let me merge this first. We need to keep an eye on the nightly result for branch HBASE-27109, to fix the unstable tests. Thanks. |
…5157) Signed-off-by: Liangjun He <heliangjun@apache.org>
…5157) Signed-off-by: Liangjun He <heliangjun@apache.org>
…5157) Signed-off-by: Liangjun He <heliangjun@apache.org>
…5157) Signed-off-by: Liangjun He <heliangjun@apache.org>
…5157) Signed-off-by: Liangjun He <heliangjun@apache.org>
…5157) Signed-off-by: Liangjun He <heliangjun@apache.org>
…5157) Signed-off-by: Liangjun He <heliangjun@apache.org>
…5157) Signed-off-by: Liangjun He <heliangjun@apache.org>
…5157) Signed-off-by: Liangjun He <heliangjun@apache.org>
…5157) Signed-off-by: Liangjun He <heliangjun@apache.org>
…5157) Signed-off-by: Liangjun He <heliangjun@apache.org>
…5157) Signed-off-by: Liangjun He <heliangjun@apache.org>
…5157) Signed-off-by: Liangjun He <heliangjun@apache.org>
…5157) Signed-off-by: Liangjun He <heliangjun@apache.org>
No description provided.