[
https://issues.apache.org/jira/browse/HBASE-18662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16160011#comment-16160011
]
Ashish Singhi commented on HBASE-18662:
---------------------------------------
I have checked all the confs all looks good to me except below two.
{{hbase.client.max.perserver.tasks}} was changed to 2 from 5 as part of
HBASE-9843 and {{hbase.normalizer.period}} was changed to 300000 from 180000 as
part of HBASE-15065. I think (not sure) may be the contributor missed to update
value in hbase-default.xml. If the value changed in those jiras makes sense
then I think we should update the values in hbase-default.xml file.
[~nkeywal], [~tedyu], [~stack] can you let us know which value to actually
refer ? Thank you.
> The default values for many configuration items in the code are not
> consistent with hbase-default.xml
> -----------------------------------------------------------------------------------------------------
>
> Key: HBASE-18662
> URL: https://issues.apache.org/jira/browse/HBASE-18662
> Project: HBase
> Issue Type: Improvement
> Reporter: Yun Zhao
> Assignee: Yun Zhao
> Priority: Minor
> Fix For: 2.0.0-alpha-3
>
> Attachments: HBASE-18662.master.002.patch
>
>
> Such as
> {code}
> hbase.ipc.server.callqueue.handler.factor
> hbase.regionserver.logroll.errors.tolerated
> hbase.regionserver.region.split.policy
> zookeeper.session.timeout
> hbase.client.retries.number
> hbase.client.max.perserver.tasks
> hbase.client.keyvalue.maxsize
> hbase.normalizer.period
> hbase.hstore.blockingStoreFiles
> hbase.snapshot.restore.take.failsafe.snapshot
> hbase.lease.recovery.dfs.timeout
> hbase.rest.filter.classes
> hbase.http.max.threads
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
