Uh oh!
There was an error while loading. Please reload this page.
HBASE-27535: Separate slowlog thresholds for scans vs other requests - #5188
Conversation
Apache-HBase
commented
Apr 17, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Apr 18, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Apr 18, 2023
🎊 +1 overall
This message was automatically generated. |
rmdmattingly
commented
Apr 19, 2023
@virajjasani if you have any feedback here then I'd definitely appreciate it! Thank you in advance 😄 |
virajjasani
left a comment
There was a problem hiding this comment.
Left minor nits, otherwise looks good
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.
Apache-HBase
commented
Apr 20, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Apr 20, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Apr 20, 2023
🎊 +1 overall
This message was automatically generated. |
virajjasani
left a comment
There was a problem hiding this comment.
+1, could you also add the new configs descriptions to https://github.com/apache/hbase/blob/master/src/main/asciidoc/_chapters/ops_mgt.adoc ?
(after hbase.ipc.warn.response.time and hbase.ipc.warn.response.size)
| ==== Configuration | ||
| There are two configuration knobs that can be used to adjust the thresholds for when queries are logged. | ||
| There are four configuration knobs that can be used to adjust the thresholds for when queries are logged. |
There was a problem hiding this comment.
Can you add 1-2 more sentences here explaining why Scan gets its own? For example "Two knobs allow controlling the size and time threshold for all queries. Since Scans can often be larger and slower than other queries, there is an additional two knobs for setting a different threshold for those."
Apache-HBase
commented
Apr 21, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Apr 21, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Apr 21, 2023
💔 -1 overall
This message was automatically generated. |
Apache-HBase
commented
Apr 21, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Apr 22, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Apr 22, 2023
🎊 +1 overall
This message was automatically generated. |
virajjasani
commented
Apr 22, 2023
Thanks @rmdmattingly and @bbeaudreault !! |
…5188) Signed-off-by: Bryan Beaudreault <bbeaudreault@apache.org> Signed-off-by: Viraj Jasani <vjasani@apache.org>
…pache#5188) Signed-off-by: Bryan Beaudreault <bbeaudreault@apache.org> Signed-off-by: Viraj Jasani <vjasani@apache.org>
HBASE-27535
Scans by their nature are able to more efficiently pull back larger response sizes than gets. They also may take longer to execute than other request types. We should make it possible to configure a separate threshold for response time and response time for scans. This will allow us to tune down the thresholds for others without adding unnecessary noise for requests which are known to be slower/bigger.
This PR introduces two new dynamically configurable keys:
hbase.ipc.warn.response.time.scanhbase.ipc.warn.response.size.scanBy default, scans will fallback to using the values of the original keys without a
.scansuffix. Because of this fallback this change is a no-op by default.I've loaded this changeset onto a test cluster and verified the intended behavior, both in the case where these values are specified and unspecified.
cc @bbeaudreault