You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2022/03/10 15:32:00 UTC

[jira] [Reopened] (HBASE-26814) Default StoreHotnessProtector to off, with logs to guide when to turn it on

     [ https://issues.apache.org/jira/browse/HBASE-26814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Duo Zhang reopened HBASE-26814:
-------------------------------

For addressing the spotbugs warnings.

> 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
>            Assignee: 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 [~andrew.purtell@gmail.com] 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)