hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
Date Mon, 29 Apr 2013 04:04:16 GMT

    [ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644248#comment-13644248
] 

Anoop Sam John commented on HBASE-8450:
---------------------------------------

bq.My worry is that doing the latter would overwhelm and hide configurations folks might want
to actually tweek.
Yes Stack. I agree to your concern. I too have that.. We should add configs to some place
which is accessible to the users.(May be not in hbase-default.xml) Now to know a config exists
the only way is to go through the code which might be difficult for all the users. I have
seen in Hive they have a hive-default.xml.template file or so in which all new configs are
added. We can go in some way in which all configs are documented. Else we dev team itself
wont be knowing all the config items or forgetting certain items. 
                
> Update hbase-default.xml and general recommendations to better suit current hw, h2, experience,
etc.
> ----------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-8450
>                 URL: https://issues.apache.org/jira/browse/HBASE-8450
>             Project: HBase
>          Issue Type: Task
>          Components: Usability
>            Reporter: stack
>            Priority: Critical
>             Fix For: 0.95.1
>
>         Attachments: 8450.txt
>
>
> This is a critical task we need to do before we release; review our defaults.
> On cursory review, there are configs in hbase-default.xml that no longer have matching
code; there are some that should be changed because we know better now and others that should
be amended because hardware and deploys are bigger than they used to be.
> We could also move stuff around so that the must-edit stuff is near the top (zk quorum
config. is mid-way down the page) and beef up the descriptions -- especially since these descriptions
shine through in the refguide.
> Lastly, I notice that our tgz does not "include" an hbase-default.xml other than the
one bundled up in the jar.  Maybe we should make it more accessible.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message