- 
                Notifications
    You must be signed in to change notification settings 
- Fork 3.4k
HBASE-24781 Clean up peer metrics when disabling peer #4997
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. | 
| HBASE-27463 is not enough to fix the metrics problem? | 
| Thank you, I was not aware of HBASE-27463. The PR #4863 does seem to address HBASE-24781 too. | 
| @frostruan Mind taking a look at this PR? Thanks. | 
| Thanks for the invitation Duo @Apache9 I think it depends on whether we want to keep the old metric information when refresh replication source. If so, then I think this is a great improvement, what only needs to be done is to remind the user of our behavior change in the release note. And also, we may need to change the clearMetric flag to false to avoid calling singleSourceSource.clear() in https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSourceManager.java#L470 ? What do you think ? @mosmeh | 
| You are correct. Updated to clearMetric=false. | 
| 🎊 +1 overall 
 
 This message was automatically generated. | 
| 🎊 +1 overall 
 
 This message was automatically generated. | 
| 💔 -1 overall 
 
 This message was automatically generated. | 
| @Apache9 @frostruan Let's decide whether we want to keep the old metric information. I personally want to, as I think that is the consistent behavior with HBase 1.x. | 
| looks like a great improvement ! +1 | 
| 💔 -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. | 
Co-authored-by: Yuta Imazu <[email protected]> Signed-off-by: Duo Zhang <[email protected] (cherry picked from commit ef6a113)
Co-authored-by: Yuta Imazu <[email protected]> Signed-off-by: Duo Zhang <[email protected] (cherry picked from commit ef6a113)
Co-authored-by: Yuta Imazu <[email protected]> Signed-off-by: Duo Zhang <[email protected] (cherry picked from commit ef6a113)
| @mosmeh Do you have an apache jira id so I can assign the jira to you? https://issues.apache.org/jira If not, please send an email to [email protected] so I can create an jira account for you. Thanks. | 
| 
 Done. Thanks! | 
Co-authored-by: Yuta Imazu <[email protected]> Signed-off-by: Duo Zhang <[email protected] (cherry picked from commit ef6a113) (cherry picked from commit 3fab7b3) Change-Id: If218991493fb9af09b1c825041cc68b7f6b9df5f
https://issues.apache.org/jira/browse/HBASE-24781
Since #778,
refreshSourcesstopped callingmetrics.clear().However, some of the tasks in
clear(), including decrementingsizeOfLogQueue, still have to be performed byrefreshSources.