Uh oh!
There was an error while loading. Please reload this page.
HBASE-27968 add JvmPauseMonitor in hbase-client - #5319
Conversation
Apache-HBase
commented
Jul 9, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Jul 9, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Jul 9, 2023
🎊 +1 overall
This message was automatically generated. |
wchevreuil
left a comment
There was a problem hiding this comment.
Should we also add it for ConnectionImplementation?
| private final String metricsScope; | ||
| private final Optional<MetricsConnection> metrics; | ||
| private JvmPauseMonitor pauseMonitor; |
There was a problem hiding this comment.
Make this a singleton, instead? In the case of applications opening or pooling multiple connections, we don't need a separate JvmPauseMonitor per connection, just a single one for the whole application.
There was a problem hiding this comment.
Good idea ! But if so, we may need to consider adding a reference count to pauseMonitor. Only when all connections that refer to it are no longer active, we can stop it . Or we can keep it all the time , even all the connections are closed ?
There was a problem hiding this comment.
Yeah, I think we don't need to stop it when connection is closed, it may be useful to have it running for as long the client application runs.
frostruan
commented
Jul 10, 2023
Thanks for the review @wchevreuil Sorry, I didn't find the |
Apache-HBase
commented
Jul 10, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jul 10, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Jul 10, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Jul 11, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jul 11, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jul 11, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Jul 12, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Jul 12, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Jul 12, 2023
💔 -1 overall
This message was automatically generated. |
| private JvmPauseMonitorSource metricsSource; | ||
| private final JvmPauseMonitorSource metricsSource; | ||
| public static synchronized JvmPauseMonitor getInstance(Configuration conf) { |
There was a problem hiding this comment.
Why change it to singleton? What if we pass different Configuration here?
There was a problem hiding this comment.
There are two reasons.
@wchevreuil mentioned that our user may open multiple connections, however only one pause monitor is enough for a process. More details please see here
There was a problem hiding this comment.
If we only want one JvmPauseMonitor in process, then we should not bind it to a connection? Just add a utility method to enable jvm pause monitor is enough?
There was a problem hiding this comment.
Ok. Let me try to fix this. Thanks Duo ! @Apache9
wchevreuil
commented
Jul 13, 2023
Yeah, you are right. My bad, I was looking at older branches. LGTM, assuming the UT failures are unrelated. |
No description provided.