[
https://issues.apache.org/jira/browse/HBASE-26814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503814#comment-17503814
]
Andrew Kyle Purtell commented on HBASE-26814:
---------------------------------------------
[~bbeaudreault] It is simple to default this to off, by setting the put
threshold to 0, but after that is don,eit is not possible to warn when it would
have otherwise triggered because the threshold was changed. This would seem to
call for a new configuration setting to enable or disable this independent from
the threshold. That could be fine but proliferation of configuration settings
is something we have discussed in the past.
> Default StoreHotnessProtector to off, with logs to guide when to turn it on
> ---------------------------------------------------------------------------
>
> Key: HBASE-26814
> URL: https://issues.apache.org/jira/browse/HBASE-26814
> Project: HBase
> Issue Type: Improvement
> Reporter: Bryan Beaudreault
> Priority: Major
> Fix For: 2.5.0, 2.6.0, 3.0.0-alpha-3
>
>
> As discussed in HBASE-26522 and somewhat in HBASE-26575,
> StoreHotnessProtector is too conservative. One can easily trigger
> RegionTooBusyException on an otherwise idle regionserver with relatively
> small amount of traffic. The idea behind this protection is good, but it
> needs to take into account current load in order to warrant being enabled by
> default.
> Until it's improved as such, we should change it to default off. One thing we
> can do to help drive usage would be to add warning logs when it would have
> triggered. Operators who are diagnosing performance issues will naturally
> look at the logs and see indication of a potential tool for mitigation.
> cc [[email protected]]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
