-
Notifications
You must be signed in to change notification settings - Fork 3.4k
HBASE-24681 Remove the cache walsById/walsByIdRecoveredQueues from Re… #2019
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
Conversation
|
🎊 +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. |
|
🎊 +1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
…plicationSourceManager
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
wchevreuil
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Per HBASE-24666 design doc, ReplicationSourceManager should concern with adding wals to the ReplicationQueueStorage, so could we simply remove some of the methods related with ReplicationSources control, since ReplicationSources are now run from ReplicationServers? Apparently those methods are the only ones using this walsById cache.
|
Yes. But I plan to implement it piece by piece and make sure all ut passed, it will be easy for review. Will finish the complete "decouple" in the follow on issues. Meanwhile, I will add a implementation plan section in the design doc. Thanks. |
…plicationSourceManager (#2019) Signed-off-by: Wellington Chevreuil <[email protected]>
…plicationSourceManager (#2019) Signed-off-by: Wellington Chevreuil <[email protected]>
…plicationSourceManager (#2019) Signed-off-by: Wellington Chevreuil <[email protected]>
…plicationSourceManager (apache#2019) Signed-off-by: Wellington Chevreuil <[email protected]>
…plicationSourceManager (apache#2019) Signed-off-by: Wellington Chevreuil <[email protected]>
…plicationSourceManager (apache#2019) Signed-off-by: Wellington Chevreuil <[email protected]>
…plicationSourceManager (apache#2019) Signed-off-by: Wellington Chevreuil <[email protected]>
…plicationSourceManager (apache#2019) Signed-off-by: Wellington Chevreuil <[email protected]>
…plicationSourceManager (apache#2019) Signed-off-by: Wellington Chevreuil <[email protected]>
…plicationSourceManager (#2019) Signed-off-by: Wellington Chevreuil <[email protected]>
…plicationSourceManager (apache#2019) Signed-off-by: Wellington Chevreuil <[email protected]>
…plicationSourceManager (#2019) Signed-off-by: Wellington Chevreuil <[email protected]>
…plicationSourceManager (#2019) Signed-off-by: Wellington Chevreuil <[email protected]>
…plicationSourceManager (#2019) Signed-off-by: Wellington Chevreuil <[email protected]>
…plicationSourceManager (#2019) Signed-off-by: Wellington Chevreuil <[email protected]>
…plicationSourceManager (#2019) Signed-off-by: Wellington Chevreuil <[email protected]>
…plicationSourceManager (#2019) Signed-off-by: Wellington Chevreuil <[email protected]>
…plicationSourceManager (#2019) Signed-off-by: Wellington Chevreuil <[email protected]>
…plicationSourceManager (#2019) Signed-off-by: Wellington Chevreuil <[email protected]>
…plicationSourceManager