hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10074) consolidate and improve capacity/sizing documentation
Date Thu, 05 Dec 2013 04:57:35 GMT

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

stack commented on HBASE-10074:
-------------------------------

The way I've been doing doc. is just commiting on trunk and then copying it back whenever
I make a release.  This works for now while the doc. is x-version.  One day it won't.  Then
we can commit each doc change to each branch (version-specific recommendations are called
out in the doc usually...)

> consolidate and improve capacity/sizing documentation
> -----------------------------------------------------
>
>                 Key: HBASE-10074
>                 URL: https://issues.apache.org/jira/browse/HBASE-10074
>             Project: HBase
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 0.98.0
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>             Fix For: 0.99.0
>
>         Attachments: HBASE-10074.01.patch, HBASE-10074.patch
>
>
> Region count description is in config section; region size description is in architecture
sections; both of these have a lot of good technical details, but imho we could do better
in terms of admin-centric advice. 
> Currently, there's a nearly-empty capacity section; I'd like to rewrite it to consolidate
capacity planning/sizing/region sizing information, and some basic configuration pertaining
to it.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message