You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/12 18:53:00 UTC

[jira] [Resolved] (HBASE-3944) Remove the overused hbase.server.thread.wakefrequency and replace with multiple configs. specific to context

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

Andrew Kyle Purtell resolved HBASE-3944.
----------------------------------------
    Resolution: Done

> Remove the overused hbase.server.thread.wakefrequency and replace with multiple configs. specific to context
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-3944
>                 URL: https://issues.apache.org/jira/browse/HBASE-3944
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Michael Stack
>            Priority: Major
>              Labels: beginner
>
> From LarsG up on list:
> implicitly triggers the above check. Also this
> >
> >  <property>
> >    <name>hbase.server.thread.wakefrequency</name>
> >    <value>10000</value>
> >    <description>Time to sleep in between searches for work (in milliseconds).
> >    Used as sleep interval by service threads such as log roller.
> >    </description>
> >  </property>
> >
> > which is used in this scenario to trigger the check when there is no
> > event (put/delete etc.) is quite ambiguous and warrants for a better
> > explanation. No?
> The above config. is overdone.  Remove it and make multiple individual, context-specific configs in its place.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)