[
https://issues.apache.org/jira/browse/HBASE-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15873359#comment-15873359
]
Jan Hentschel commented on HBASE-3944:
--------------------------------------
This seems to be part of HBASE-13074 which removes the remaining usages of
hbase.server.thread.wakefrequency.
> 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: stack
>
> 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
(v6.3.15#6346)
