[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248944#comment-14248944 ] Hudson commented on HBASE-8450: --- FAILURE: Integrated in HBase-TRUNK #5930 (See [https://builds.apache.org/job/HBase-TRUNK/5930/]) HBASE-9431 Set 'hbase.bulkload.retries.number' to 10 as HBASE-8450 claims (stack: rev e5d813c46b41ab4fb48d72731eb34422f260b81a) * hbase-common/src/main/resources/hbase-default.xml * hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/LoadIncrementalHFiles.java > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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 was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248920#comment-14248920 ] Hudson commented on HBASE-8450: --- SUCCESS: Integrated in HBase-1.0 #589 (See [https://builds.apache.org/job/HBase-1.0/589/]) HBASE-9431 Set 'hbase.bulkload.retries.number' to 10 as HBASE-8450 claims (stack: rev 36269b64038c6fcf076a1d8df90ea087559eb208) * hbase-common/src/main/resources/hbase-default.xml * hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/LoadIncrementalHFiles.java > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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 was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757733#comment-13757733 ] stack commented on HBASE-8450: -- [~jeffreyz] Thank you for looking. I must have messed up setting bulkload.retries. I made HBASE-9431 to change it to what this issue says it is (smile) > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757402#comment-13757402 ] Jeffrey Zhong commented on HBASE-8450: -- [~saint@gmail.com] I happened to check current defaults. The 'hbase.bulkload.retries.number' is still set as 0. Do we want the value to be set as 10? Thanks. > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13745174#comment-13745174 ] Jeffrey Zhong commented on HBASE-8450: -- Thanks [~saint@gmail.com]! HBase-9271 is a good way in order not to surprise our users later. > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13744658#comment-13744658 ] stack commented on HBASE-8450: -- [~jeffreyz] Something like a HBASE-9271? > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13744654#comment-13744654 ] stack commented on HBASE-8450: -- Well, it is in these release notes. We should probably have a doc. that goes out w/ the release that highlights the major differences. We could add a note there on this difference? > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[
https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13744617#comment-13744617
]
Jeffrey Zhong commented on HBASE-8450:
--
[~saint@gmail.com] {quote}max versions now 1 instead of 3{quote} Is there
any place we can document this? After upgraded to 0.96, the script or client
code may think data loss with statements such as {code}scan 'mytable',
{VERSIONS => 3}{code} with the same table creation statement {code}create
'mytable', 'f1'{code} ported from 0.94 code.
> 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
>Assignee: stack
>Priority: Critical
> Fix For: 0.95.1
>
> Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697583#comment-13697583 ] Anoop Sam John commented on HBASE-8450: --- I have seen one issue raised by our [~eclark] and I commented in that so as to make this change also there.. He agreed.. > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697311#comment-13697311 ] stack commented on HBASE-8450: -- [~anoop.hbase] You have a patch sir with stuff I missed? Could apply here or probably better in a new issue? > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697063#comment-13697063 ] Lars Hofhansl commented on HBASE-8450: -- Fair enough. I agree. > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697029#comment-13697029 ] Jean-Daniel Cryans commented on HBASE-8450: --- Not a big fan of late 0.94 changes to defaults. Imagine a situation where the user tweaked the memstore lower/upper limits to use that 20% of the heap we're not assigning, so now it would be >80%, and then deploys 0.94.10 via rolling restart and the RS refuse to come back up because of that. Basically the dynamics of the cluster would be different (maybe in a good way or maybe not?). To be fair, serious deploys would have those configurations tweaked so it wouldn't change anything for them. > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696108#comment-13696108 ] Lars Hofhansl commented on HBASE-8450: -- I would like to solicit opinions about whether we make some of these config changes in 0.94 as well. If so, I would suggest the following changes: + handlers 30 instead of 10 + upped memstore lower limit from .35 to .38 + bulkload retries is 10 instead of infinite + blockingstorefiles is 10 instead of 7 + block cache is 0.4 instead of 0.25 And maybe this: + major compactions are now once a week instead of once every 24 hours; they are staggered so all regionservers do not start compacting at the same time > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[
https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671133#comment-13671133
]
Anoop Sam John commented on HBASE-8450:
---
[~stack] We have changed the config values in xml file. Still in the code, some
places it refers to the old values. Sorry missed this point in the review.
{code}
HConstants
public static final float HFILE_BLOCK_CACHE_SIZE_DEFAULT = 0.25f;
MemStoreFlusher
private static final float DEFAULT_LOWER = 0.35f;
{code}
It might look confusing for developers later. We can correct this?
> 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
>Assignee: stack
>Priority: Critical
> Fix For: 0.95.1
>
> Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665531#comment-13665531 ] Nicolas Liochon commented on HBASE-8450: [~jdcryans] bq. I agree with you that setting that down to 10 would currently mean that we might retry timeouts on the region servers. What I'm wondering now is how we can make this better. Should we also tweak the default operation timeout lower? Maybe it set it higher for MR jobs? HBASE-7590 helps here, because you can set a high timeout without beeing stuck on dead servers. May be we could have different timeouts for read & writes, as read can be reexecuted without risks). But on the long term I think that the best option is around the approach of HBASE-7590: just wait, if the server is dead we will tell you... > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665363#comment-13665363 ] Hudson commented on HBASE-8450: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #540 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/540/]) HBASE-8450 Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc. (Revision 1485561) Result = FAILURE stack : Files : * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/HColumnDescriptor.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/HTableDescriptor.java * /hbase/trunk/hbase-common/src/main/resources/hbase-default.xml * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/compactions/CompactionConfiguration.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/TestMultiVersions.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestFromClientSide.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/filter/TestColumnPrefixFilter.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/filter/TestDependentColumnFilter.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/filter/TestMultipleColumnPrefixFilter.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/io/encoding/TestEncodedSeekers.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportExport.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestColumnSeeking.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegionBusyWait.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestSeekOptimizations.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationBase.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/client/TestRemoteTable.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/thrift2/TestThriftHBaseServiceHandler.java > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665268#comment-13665268 ] Hudson commented on HBASE-8450: --- Integrated in hbase-0.95-on-hadoop2 #109 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/109/]) HBASE-8450 Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc. (Revision 1485562) Result = FAILURE stack : Files : * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/HColumnDescriptor.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/HTableDescriptor.java * /hbase/branches/0.95/hbase-common/src/main/resources/hbase-default.xml * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/compactions/CompactionConfiguration.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/TestMultiVersions.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestFromClientSide.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/filter/TestColumnPrefixFilter.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/filter/TestDependentColumnFilter.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/filter/TestMultipleColumnPrefixFilter.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/io/encoding/TestEncodedSeekers.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportExport.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestColumnSeeking.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegionBusyWait.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestSeekOptimizations.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationBase.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/client/TestRemoteTable.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/thrift2/TestThriftHBaseServiceHandler.java > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664967#comment-13664967 ] Hudson commented on HBASE-8450: --- Integrated in hbase-0.95 #210 (See [https://builds.apache.org/job/hbase-0.95/210/]) HBASE-8450 Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc. (Revision 1485562) Result = SUCCESS stack : Files : * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/HColumnDescriptor.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/HTableDescriptor.java * /hbase/branches/0.95/hbase-common/src/main/resources/hbase-default.xml * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/compactions/CompactionConfiguration.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/TestMultiVersions.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestFromClientSide.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/filter/TestColumnPrefixFilter.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/filter/TestDependentColumnFilter.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/filter/TestMultipleColumnPrefixFilter.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/io/encoding/TestEncodedSeekers.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportExport.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestColumnSeeking.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegionBusyWait.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestSeekOptimizations.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationBase.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/client/TestRemoteTable.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/thrift2/TestThriftHBaseServiceHandler.java > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664934#comment-13664934 ] Hudson commented on HBASE-8450: --- Integrated in HBase-TRUNK #4138 (See [https://builds.apache.org/job/HBase-TRUNK/4138/]) HBASE-8450 Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc. (Revision 1485561) Result = SUCCESS stack : Files : * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/HColumnDescriptor.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/HTableDescriptor.java * /hbase/trunk/hbase-common/src/main/resources/hbase-default.xml * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/compactions/CompactionConfiguration.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/TestMultiVersions.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestFromClientSide.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/filter/TestColumnPrefixFilter.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/filter/TestDependentColumnFilter.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/filter/TestMultipleColumnPrefixFilter.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/io/encoding/TestEncodedSeekers.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportExport.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestColumnSeeking.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegionBusyWait.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestSeekOptimizations.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationBase.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/client/TestRemoteTable.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/thrift2/TestThriftHBaseServiceHandler.java > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664825#comment-13664825 ] Anoop Sam John commented on HBASE-8450: --- +1 > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664726#comment-13664726 ] Jean-Daniel Cryans commented on HBASE-8450: --- +1, will be good to put this in the hands of some devs with 0.95.1 > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664542#comment-13664542 ] stack commented on HBASE-8450: -- Thanks [~eclark]. I think I fixed the site prob. elsewhere (bad commit of a doc change). May I have another +1 since this fundamental. Let me update the release notes because it might help understand the set of changes introduced here. > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664538#comment-13664538 ] Elliott Clark commented on HBASE-8450: -- I'm +1 assuming that the mvn site failure isn't related. > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[
https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664512#comment-13664512
]
Hadoop QA commented on HBASE-8450:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12584369/8450v5.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 45 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces lines longer than
100
{color:red}-1 site{color}. The patch appears to cause mvn site goal to
fail.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/5785//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5785//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5785//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5785//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5785//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5785//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5785//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5785//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5785//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5785//console
This message is automatically generated.
> 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
>Assignee: stack
>Priority: Critical
> Fix For: 0.95.1
>
> Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664473#comment-13664473 ] stack commented on HBASE-8450: -- Just to add that I had to fix a bunch of unit tests because they were expecting max values to be the default 3 and because a few tests were expecting one encoding type only in block cache (w/ blooms on, it has blocks in the cache w/ encoding NONE which was messing up some expectations) > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13663737#comment-13663737 ] stack commented on HBASE-8450: -- Let me put back major compactions on a week period for now. I added jitter of 0.5 so hopefully the major compactions are spread over the week rather than all happening together monday morning just as the load is coming on. Let me fix the tests broke by changed defaults and post another patch. > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662599#comment-13662599 ] Enis Soztutar commented on HBASE-8450: -- I would also +1 for 1 week major compactions, rather than disabling that. We should definitely do a release note on this for default max versions. > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662369#comment-13662369 ] Jean-Daniel Cryans commented on HBASE-8450: --- bq. From what I've seen, it's not that uncommon to have something above 60s, and retrying just adds some workload on the server? So originally I opened HBASE-4462 so that we stop retrying those timeouts, but people agreed that HBASE-2937 (the operation timeout included in 0.92.0) was covering that case. Passing an operation timeout actually changes the rpc timeout at the same time, and it does cancel the retries in ServerCallable (although in trunk I found out we don't change the rpc timeout, see HBASE-8581). I agree with you that setting that down to 10 would currently mean that we might retry timeouts on the region servers. What I'm wondering now is how we can make this better. Should we also tweak the default operation timeout lower? Maybe it set it higher for MR jobs? > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662296#comment-13662296 ] Jean-Daniel Cryans commented on HBASE-8450: --- bq. That is true too. How frequently does that happen? Unfortunately it really depends on how big the files are in the region such that it would decide to include all the files. > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662295#comment-13662295 ] Lars Hofhansl commented on HBASE-8450: -- Just saw this comment: bq. second, frequently compactions are promoted to major compaction because all files are selected so deletes would get purged That is true too. How frequently does that happen? > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662290#comment-13662290 ] Lars Hofhansl commented on HBASE-8450: -- This is a bit of a fundamental flaw in HBase. True, if you never delete stuff, you don't need major compactions. But if you do, especially when you place a lot of delete markers, you definitely want major compactions. Sergey's striped compaction will make this a moot point, but until then it seems that we need to be able to clean up. Major compactions also help to eventually regain data locality if regions were moved. Whether it's a day or a week almost does not matter. A week seems fine to me as default. Can always document to disable major compactions if you do not delete a lot. Otherwise we need to introduce a "Routine Maintenance" section to the book and instruct to run major compactions "when it makes sense" (they have no metric to go by really). Maybe a way to tackle this is to have "remove delete marker" compaction, which will still read all files but only rewrites HFile when a delete marker was found. > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[
https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662234#comment-13662234
]
Hadoop QA commented on HBASE-8450:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12583855/8450v5.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 15 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces lines longer than
100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.io.encoding.TestEncodedSeekers
org.apache.hadoop.hbase.regionserver.TestHRegionBusyWait
org.apache.hadoop.hbase.security.access.TestAccessController
org.apache.hadoop.hbase.TestMultiVersions
org.apache.hadoop.hbase.client.TestFromClientSideWithCoprocessor
org.apache.hadoop.hbase.regionserver.TestHRegion
org.apache.hadoop.hbase.replication.TestReplicationSmallTests
org.apache.hadoop.hbase.client.TestFromClientSide
org.apache.hadoop.hbase.regionserver.TestGetClosestAtOrBefore
org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler
org.apache.hadoop.hbase.mapreduce.TestImportExport
org.apache.hadoop.hbase.rest.client.TestRemoteTable
org.apache.hadoop.hbase.regionserver.TestSeekOptimizations
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/5752//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5752//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5752//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5752//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5752//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5752//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5752//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5752//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5752//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5752//console
This message is automatically generated.
> 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
>Assignee: stack
>Priority: Critical
> Fix For: 0.95.1
>
> Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.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 --
> espe
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662205#comment-13662205 ] stack commented on HBASE-8450: -- [~lhofhansl] Then what would you suggest for a major compaction interval? If you think a week, then I'd say might as well just turn it off. If you say a day, i'd suggest that is too frequent rewriting all of a deploys' data. I can add to the refguide a section on "If your scans start to slow over time..." Would that help? Looks like there are more tests that expect max versions of 3 as default. Fixing... new patch coming. > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662170#comment-13662170 ] Lars Hofhansl commented on HBASE-8450: -- I'd still be concerned about disabling major compactions. If kvs are deleted the delete markers will hang around forever slowing down scans. > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[
https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662142#comment-13662142
]
Hadoop QA commented on HBASE-8450:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12583846/8450v3.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces lines longer than
100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.regionserver.TestColumnSeeking
org.apache.hadoop.hbase.filter.TestColumnPrefixFilter
org.apache.hadoop.hbase.filter.TestDependentColumnFilter
org.apache.hadoop.hbase.filter.TestMultipleColumnPrefixFilter
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/5751//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5751//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5751//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5751//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5751//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5751//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5751//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5751//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5751//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5751//console
This message is automatically generated.
> 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
>Assignee: stack
>Priority: Critical
> Fix For: 0.95.1
>
> Attachments: 8450.txt, 8450v2.txt, 8450v3.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662134#comment-13662134 ] Nicolas Liochon commented on HBASE-8450: I would even increase the number of retries to 30. +1 for zookeeper timeout. I don't understand this one: + rpc timeout is 10seconds instead of 60seconds >From what I've seen, it's not that uncommon to have something above 60s, and >retrying just adds some workload on the server? > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.txt, 8450v3.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662095#comment-13662095 ] stack commented on HBASE-8450: -- [~lhofhansl] On delete marker never getting deleted, my thinking is that this would not be the end of the world and second, frequently compactions are promoted to major compaction because all files are selected so deletes would get purged (The general call is that disabling major compactions will be overall better than retention of deletes; do you disagree w/ this?). On the suggestion that FAST_DIFF slows down scan, let me put up a new patch that does not enable it; your comment puts it into that bucket of configs that we should change only after we do some testing. Let me make a new patch. > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[
https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661791#comment-13661791
]
Hadoop QA commented on HBASE-8450:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12583791/8450v2.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces lines longer than
100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.filter.TestDependentColumnFilter
org.apache.hadoop.hbase.filter.TestMultipleColumnPrefixFilter
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/5745//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5745//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5745//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5745//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5745//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5745//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5745//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5745//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/5745//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5745//console
This message is automatically generated.
> 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
>Assignee: stack
>Priority: Critical
> Fix For: 0.95.1
>
> Attachments: 8450.txt, 8450v2.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661779#comment-13661779 ] Lars Hofhansl commented on HBASE-8450: -- Are these good defaults: bq. Turned off major compactions. bq. Enabled FAST_DIFF prefix as default. The former will lead to delete marker to *never* get deleted. The latter will make scanning slower. bq. Made default minimum versions 2 instead of 3. I assume you meant maximum versions? Why not just set it to 1 by default? > 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 >Assignee: stack >Priority: Critical > Fix For: 0.95.1 > > Attachments: 8450.txt, 8450v2.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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[
https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661693#comment-13661693
]
stack commented on HBASE-8450:
--
[~dsw] Yeah, there are a class of changes that we need to experiment w/ under
load; e.g. the WAL size.
On the making it more lively, I'll make it 100ms rather 1000ms for pause but
will up the retries to 20. Because of our expotential backoff, we end up
waiting about the same time. Here is what happens currently:
{code}
4 testTimeout(org.apache.hadoop.hbase.client.TestClientNoCluster) Time
elapsed: 40.055 sec <<< ERROR!
5 org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed after
attempts=10, exceptions:
6 Sun May 19 16:01:29 PDT 2013,
org.apache.hadoop.hbase.client.ScannerCallable@20d12eea,
org.apache.hadoop.hbase.exceptions.RegionServerStoppedException: From Mockito
7 Sun May 19 16:01:30 PDT 2013,
org.apache.hadoop.hbase.client.ScannerCallable@20d12eea,
org.apache.hadoop.hbase.exceptions.RegionServerStoppedException: From Mockito
8 Sun May 19 16:01:31 PDT 2013,
org.apache.hadoop.hbase.client.ScannerCallable@20d12eea,
org.apache.hadoop.hbase.exceptions.RegionServerStoppedException: From Mockito
9 Sun May 19 16:01:32 PDT 2013,
org.apache.hadoop.hbase.client.ScannerCallable@20d12eea,
org.apache.hadoop.hbase.exceptions.RegionServerStoppedException: From Mockito
10 Sun May 19 16:01:34 PDT 2013,
org.apache.hadoop.hbase.client.ScannerCallable@20d12eea,
org.apache.hadoop.hbase.exceptions.RegionServerStoppedException: From Mockito
11 Sun May 19 16:01:36 PDT 2013,
org.apache.hadoop.hbase.client.ScannerCallable@20d12eea,
org.apache.hadoop.hbase.exceptions.RegionServerStoppedException: From Mockito
12 Sun May 19 16:01:40 PDT 2013,
org.apache.hadoop.hbase.client.ScannerCallable@20d12eea,
org.apache.hadoop.hbase.exceptions.RegionServerStoppedException: From Mockito
13 Sun May 19 16:01:44 PDT 2013,
org.apache.hadoop.hbase.client.ScannerCallable@20d12eea,
org.apache.hadoop.hbase.exceptions.RegionServerStoppedException: From Mockito
14 Sun May 19 16:01:52 PDT 2013,
org.apache.hadoop.hbase.client.ScannerCallable@20d12eea,
org.apache.hadoop.hbase.exceptions.RegionServerStoppedException: From Mockito
15 Sun May 19 16:02:08 PDT 2013,
org.apache.hadoop.hbase.client.ScannerCallable@20d12eea,
org.apache.hadoop.hbase.exceptions.RegionServerStoppedException: From Mockito
16
17 ,...at
org.apache.hadoop.hbase.client.ServerCallable.withRetries(ServerCallable.java:197)
{code}
Here is w/ 100ms pause and 20 retries:
{code}
2 Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 37.124 sec
<<< FAILURE!
3 testTimeout(org.apache.hadoop.hbase.client.TestClientNoCluster) Time
elapsed: 36.884 sec <<< ERROR!
4 org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed after
attempts=20, exceptions:
5 Sun May 19 16:25:02 PDT 2013,
org.apache.hadoop.hbase.client.ScannerCallable@5edf2d38,
org.apache.hadoop.hbase.exceptions.RegionServerStoppedException: From Mockito
6 Sun May 19 16:25:03 PDT 2013,
org.apache.hadoop.hbase.client.ScannerCallable@5edf2d38,
org.apache.hadoop.hbase.exceptions.RegionServerStoppedException: From Mockito
7 Sun May 19 16:25:03 PDT 2013,
org.apache.hadoop.hbase.client.ScannerCallable@5edf2d38,
org.apache.hadoop.hbase.exceptions.RegionServerStoppedException: From Mockito
8 Sun May 19 16:25:03 PDT 2013,
org.apache.hadoop.hbase.client.ScannerCallable@5edf2d38,
org.apache.hadoop.hbase.exceptions.RegionServerStoppedException: From Mockito
9 Sun May 19 16:25:03 PDT 2013,
org.apache.hadoop.hbase.client.ScannerCallable@5edf2d38,
org.apache.hadoop.hbase.exceptions.RegionServerStoppedException: From Mockito
10 Sun May 19 16:25:03 PDT 2013,
org.apache.hadoop.hbase.client.ScannerCallable@5edf2d38,
org.apache.hadoop.hbase.exceptions.RegionServerStoppedException: From Mockito
11 Sun May 19 16:25:04 PDT 2013,
org.apache.hadoop.hbase.client.ScannerCallable@5edf2d38,
org.apache.hadoop.hbase.exceptions.RegionServerStoppedException: From Mockito
12 Sun May 19 16:25:04 PDT 2013,
org.apache.hadoop.hbase.client.ScannerCallable@5edf2d38,
org.apache.hadoop.hbase.exceptions.RegionServerStoppedException: From Mockito
13 Sun May 19 16:25:05 PDT 2013,
org.apache.hadoop.hbase.client.ScannerCallable@5edf2d38,
org.apache.hadoop.hbase.exceptions.RegionServerStoppedException: From Mockito
14 Sun May 19 16:25:06 PDT 2013,
org.apache.hadoop.hbase.client.ScannerCallable@5edf2d38,
org.apache.hadoop.hbase.exceptions.RegionServerStoppedException: From Mockito
15 Sun May 19 16:25:10 PDT 2013,
org.apache.hadoop.hbase.client.ScannerCallable@5edf2d38,
org.apache.hadoop.hbase.exceptions.RegionServerStoppedException: From Mockito
16 Sun May 19 16:25:13 PDT 2013,
org.apache.hadoop.hbase.client.ScannerCallable@5edf2d38,
org.apache.hadoop.hbase.exceptions.RegionServerStoppedException: From Mockito
17 Su
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13658829#comment-13658829 ] David S. Wang commented on HBASE-8450: -- What's the plan to validate any changes that are made here? e.g. throw code onto a cluster of size X with reasonably-modern specs, run YCSB workload , then change defaults, reboot entire cluster, and run same workloads? That may cover some performance-related areas, but not sure what else to do to validate. > 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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[
https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656721#comment-13656721
]
binlijin commented on HBASE-8450:
-
{quote}
Now that I think about it more, it might make sense to keep bigger logs but
keep the block size itself low. For example, have
hbase.regionserver.hlog.blocksize=64MB but
hbase.regionserver.logroll.multiplier=3.95 instead of 0.95.
{quote}
If this have a good performance, so may be this is a good choice right now.
Jean-Daniel Cryans
> 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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656679#comment-13656679 ] Jean-Daniel Cryans commented on HBASE-8450: --- bq. No, i do not consider this method, according to HBASE-1394 we should have less block transition. 1394 is old and unrelated, we did 1MB blocks because we didn't have durability. bq. So, we should have muti hlog, if one is slow, use the other one. I agree we should get HBASE-5699 but we don't have it at the moment so it won't help. > 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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[
https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656628#comment-13656628
]
binlijin commented on HBASE-8450:
-
No, i do not consider this method, according to HBASE-1394 we should have less
block transition.
{quote}
Also, when I tested bigger block sizes for the HLogs, I saw that it had
detrimental effects in heavy writes situation because you spend more time
writing to each log, meaning that if you have a slow pipeline it stays slow for
a longer amount of time. The overall throughput is worse.
{quote}
So, we should have muti hlog, if one is slow, use the other one.
> 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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[
https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656219#comment-13656219
]
Jean-Daniel Cryans commented on HBASE-8450:
---
{quote}
The bigger block size, the lesser namenode rpc call.
We have a cluster with hbase.regionserver.hlog.blocksize=128m and the write
performance is improved a lot compare with
hbase.regionserver.hlog.blocksize=64m, the cell is big and most is 15K+.
{quote}
I don't think less RPCs to the NN really matters a lot here, other parts of
HBase abuse the NN a lot more, but most likely your write performance improved
because you are spending less time locking when rolling the logs. I pushed this
to the extreme and tried 1GB and 2GB blocksizes and that's when I got the bad
performance mostly.
Now that I think about it more, it might make sense to keep bigger logs but
keep the block size itself low. For example, have
hbase.regionserver.hlog.blocksize=64MB but
hbase.regionserver.logroll.multiplier=3.95 instead of 0.95. Is this something
you have tried or considered [~aoxiang]?
> 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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655419#comment-13655419 ] binlijin commented on HBASE-8450: - We have a cluster with hbase.regionserver.hlog.blocksize=128m and the write performance is improved a lot compare with hbase.regionserver.hlog.blocksize=64m, the cell is big and most is 15K+. > 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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655418#comment-13655418 ] binlijin commented on HBASE-8450: - If we adjust hbase.regionserver.hlog.blocksize, the number of logs should be adjusted together. > 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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655417#comment-13655417 ] binlijin commented on HBASE-8450: - The bigger block size, the lesser namenode rpc call. We have a cluster with hbase.regionserver.hlog.blocksize=128m and the write performance is improved a lot with hbase.regionserver.hlog.blocksize=64m, the cell is big and most is 15K+. > 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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655341#comment-13655341 ] Jean-Daniel Cryans commented on HBASE-8450: --- [~aoxiang] if you change the block size but not the number of logs it means it will take longer to replay logs by default. Is this what you want? Maybe you do, but you don't explain why you want to change it. Also, when I tested bigger block sizes for the HLogs, I saw that it had detrimental effects in heavy writes situation because you spend more time writing to each log, meaning that if you have a slow pipeline it stays slow for a longer amount of time. The overall throughput is worse. > 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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655324#comment-13655324 ] stack commented on HBASE-8450: -- [~aoxiang] Why you think we need bigger block size? Changing it will ripple through out (larger WALs, etc.). I am not averse, just would like a reason. Thakns. > 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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655148#comment-13655148 ] binlijin commented on HBASE-8450: - HLog - hbase.regionserver.hlog.blocksize and dfs.block.size = 128M or 256M - io.bytes.per.checksum = 4096 > 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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655109#comment-13655109 ] Enis Soztutar commented on HBASE-8450: -- bq. Also are we adding all the configs to xml when it is getting added to code? I doubt this.. I have checked with 94 code base some time back and I was able to find some of the configs only referred in code but not in hbase-default.xml I agree to the concern. I always saw this as a three tiered approach. (1)There are configs which are changed in every hbase-site. (2) There are some configs that you may or may not want to changed. (3) And there are configs that only if you know the code, and something crazy happens, you want to change it. For 1, and 2, they should live in hbase-default. for 3, I agree with Stack, that we should not pollute hbase-default too much. However, I have seen some (2) cases but the config was not in hbase-default. I think we should just fix those cases. > 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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653130#comment-13653130 ] Elliott Clark commented on HBASE-8450: -- bq.hbase.hstore.compactionThreshold=5: we now have a better compaction algorithm, maybe it's worth keeping more files around and be more efficient about the whole process? I would disagree here. Better to choose fewer files and be less spiky on io and latency. Though upping the number of blocking files seems ok. * Lower the number of versions on a table by default. Most new users don't really need three. I think putting it at 2 by default helps users know the feature is there without wasting space. * Turn on bloom filters. (ROW) > 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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[
https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653106#comment-13653106
]
Nick Dimiduk commented on HBASE-8450:
-
{quote}
- hfile.block.cache.size=0.4: Since we let users dedicate up to 80% of the heap
for the block cache and Memstores, we should fully use that space by default.
I've stopped counting the numbers I've told people that they had all this
memory that's not being used because they were keeping the configs default...
Right now we're at 25/40 so I'd just bump up the block cache to 40. Even better
would be doing HBASE-5349...
- hbase.regionserver.handler.count=50: or it could be 100, I don't really have
data on this.
- hbase.client.pause=100: make everything snappier? might want to bump up the
number of retries. I don't have data on this.
hbase.rpc.timeout=1: snappier I said!
{quote}
+1 for the above.
- hbase.client.write.buffer at 2M plus hbase.regionserver.handler.count at 10
sounds conservative to me, even considering JD's block cache size tweak.
- hbase.bulkload.retries.number I recall seeing a ticket where the unlimited
retries was causing havoc, but I cannot find it this morning.
- hbase.client.scanner.caching this number is entirely arbitrary, given
variance in data shape. Do we still like 100?
- hbase.hregion.memstore.flush.size is the same value as default hdfs block
size. dumb question: should this be slightly less than the hdfs block size in
order to accommodate headers and trailers?
- hbase.config.read.zookeeper.config can this configuration point be removed
entirely? Is there ever a reason to read zoo.cfg?
Cleaning up the file with spell-check and sort by property name would be nice
too ;)
> 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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13650278#comment-13650278 ] Jean-Daniel Cryans commented on HBASE-8450: --- hbase-default.xml: - hfile.block.cache.size=0.4: Since we let users dedicate up to 80% of the heap for the block cache and Memstores, we should fully use that space by default. I've stopped counting the numbers I've told people that they had all this memory that's not being used because they were keeping the configs default... Right now we're at 25/40 so I'd just bump up the block cache to 40. Even better would be doing HBASE-5349... - hbase.hregion.majorcompaction=0: disable major compactions, I can't remember the last time I told someone to run them more often, but just last week I told someone to either disable them or have them running weekly. - hbase.regionserver.nbreservationblocks=0: do we even want this now that we kill on OOME? - hbase.regionserver.handler.count=50: or it could be 100, I don't really have data on this. - hbase.client.pause=100: make everything snappier? might want to bump up the number of retries. I don't have data on this. - hbase.rpc.timeout=1: snappier I said! - hbase.hstore.compactionThreshold=5: we now have a better compaction algorithm, maybe it's worth keeping more files around and be more efficient about the whole process? - hbase.hstore.blockingStoreFiles=10: I'd give some room to the algo to make good choices so bumping that up too. - zookeeper.session.timeout=9: is 3 minutes still a good default? Now that we have MSLAB it's rare that I see legit GC issues. Other: - Enable bloom filters by default, will also help offsetting the higher number of files. - Set the default heap higher? 2GB? > 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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ 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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13643814#comment-13643814 ] stack commented on HBASE-8450: -- bq. Also are we adding all the configs to xml when it is getting added to code? I doubt this.. I have checked with 94 code base some time back and I was able to find some of the configs only referred in code but not in hbase-default.xml My thought was that we didn't have to do this; that we only had to add ones we thought folks might want to change. I know that there others who think otherwise, that hbase-default.xml should be a conprehensive list of all you could possibly change. My worry is that doing the latter would overwhelm and hide configurations folks might want to actually tweek. > 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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13643577#comment-13643577 ] Anoop Sam John commented on HBASE-8450: --- bq.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. +1. Also are we adding all the configs to xml when it is getting added to code? I doubt this.. I have checked with 94 code base some time back and I was able to find some of the configs only referred in code but not in hbase-default.xml > 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
[jira] [Commented] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13643493#comment-13643493 ] Lars Hofhansl commented on HBASE-8450: -- Some of this would be good for 0.94 as well. > 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
