[
https://issues.apache.org/jira/browse/HBASE-11985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15063085#comment-15063085
]
Hadoop QA commented on HBASE-11985:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12778313/HBASE-11985.patch
against master branch at commit 80fc18d2e1f72d312a4ab90a32d6e44c9b560493.
ATTACHMENT ID: 12778313
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.6.1 2.7.0
2.7.1)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not generate new
checkstyle errors.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-site goal succeeds with this
patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
{color:green}+1 zombies{color}. No zombie tests found running at the end of
the build.
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/16915//testReport/
Release Findbugs (version 2.0.3) warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/16915//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/16915//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/16915//console
This message is automatically generated.
> Document sizing rules of thumb
> ------------------------------
>
> Key: HBASE-11985
> URL: https://issues.apache.org/jira/browse/HBASE-11985
> Project: HBase
> Issue Type: Task
> Components: documentation
> Affects Versions: 2.0.0
> Reporter: Misty Stanley-Jones
> Assignee: Misty Stanley-Jones
> Fix For: 2.0.0
>
> Attachments: HBASE-11985.patch
>
>
> I'm looking for tuning/sizing rules of thumb to put in the Ref Guide.
> Info I have gleaned so far:
> A reasonable region size is between 10 GB and 50 GB.
> A reasonable maximum cell size is 1 MB to 10 MB. If your cells are larger
> than 10 MB, consider storing the cell contents in HDFS and storing a
> reference to the location in HBase. Pending MOB work for 10 MB - 64 MB window.
> When you size your regions and cells, keep in mind that a region cannot split
> across a row. If your row size is too large, or your region size is too
> small, you can end up with a single row per region, which is not a good
> pattern. It is also possible that one big column causes splits while other
> columns are tiny, and this may not be great.
> A large # of columns probably means you are doing it wrong.
> Column names need to be short because they get stored for every value
> (barring encoding). Don't need to be self-documenting like in RDBMS.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
