You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Lars George <la...@gmail.com> on 2011/06/01 16:21:19 UTC
Config Option Obsolete
Hi,
hbase.regionserver.thread.splitcompactcheckfrequency
Seems to be obsolete now that the flush is event triggered, and
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?
Lars
Re: Config Option Obsolete
Posted by Lars George <la...@gmail.com>.
Thanks Stack! My thoughts exactly.
On Wed, Jun 1, 2011 at 7:35 PM, Stack <st...@duboce.net> wrote:
> On Wed, Jun 1, 2011 at 7:21 AM, Lars George <la...@gmail.com> wrote:
>> Hi,
>>
>> hbase.regionserver.thread.splitcompactcheckfrequency
>>
>> Seems to be obsolete now that the flush is event triggered,
>
> I removed it.
>
>
>> 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?
>>
>
> Seems like this config. is use all over. Its used so much its almost
> dangerous to change -- who knows how it'd ripple through the system.
> We should obsolete it and make new individual configs whereever its
> used? I made an issue.
>
> St.Ack
>
Re: Config Option Obsolete
Posted by Stack <st...@duboce.net>.
On Wed, Jun 1, 2011 at 7:21 AM, Lars George <la...@gmail.com> wrote:
> Hi,
>
> hbase.regionserver.thread.splitcompactcheckfrequency
>
> Seems to be obsolete now that the flush is event triggered,
I removed it.
> 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?
>
Seems like this config. is use all over. Its used so much its almost
dangerous to change -- who knows how it'd ripple through the system.
We should obsolete it and make new individual configs whereever its
used? I made an issue.
St.Ack