[jira] [Commented] (HBASE-4374) Up default regions size from 256M to 1G
[ https://issues.apache.org/jira/browse/HBASE-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13135007#comment-13135007 ] Hudson commented on HBASE-4374: --- Integrated in HBase-TRUNK #2366 (See [https://builds.apache.org/job/HBase-TRUNK/2366/]) HBASE-4374 Up default regions size from 256M to 1G stack : Files : * /hbase/trunk/CHANGES.txt * /hbase/trunk/src/main/resources/hbase-default.xml Up default regions size from 256M to 1G --- Key: HBASE-4374 URL: https://issues.apache.org/jira/browse/HBASE-4374 Project: HBase Issue Type: Task Reporter: stack Priority: Blocker Fix For: 0.92.0 Attachments: 4374.txt HBASE-4365 has some discussion of why we default for a table should tend to fewer bigger regions. It doesn't look like this issue will be done for 0.92. For 0.92, lets up default region size from 256M to 1G and talk up pre-split on table creation in manual. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4374) Up default regions size from 256M to 1G
[ https://issues.apache.org/jira/browse/HBASE-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13135114#comment-13135114 ] Hudson commented on HBASE-4374: --- Integrated in HBase-0.92 #79 (See [https://builds.apache.org/job/HBase-0.92/79/]) HBASE-4374 Up default regions size from 256M to 1G stack : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/main/resources/hbase-default.xml Up default regions size from 256M to 1G --- Key: HBASE-4374 URL: https://issues.apache.org/jira/browse/HBASE-4374 Project: HBase Issue Type: Task Reporter: stack Priority: Blocker Fix For: 0.92.0 Attachments: 4374.txt HBASE-4365 has some discussion of why we default for a table should tend to fewer bigger regions. It doesn't look like this issue will be done for 0.92. For 0.92, lets up default region size from 256M to 1G and talk up pre-split on table creation in manual. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4374) Up default regions size from 256M to 1G
[ https://issues.apache.org/jira/browse/HBASE-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13134622#comment-13134622 ] Jean-Daniel Cryans commented on HBASE-4374: --- +1 Up default regions size from 256M to 1G --- Key: HBASE-4374 URL: https://issues.apache.org/jira/browse/HBASE-4374 Project: HBase Issue Type: Task Reporter: stack Priority: Blocker Fix For: 0.92.0 HBASE-4365 has some discussion of why we default for a table should tend to fewer bigger regions. It doesn't look like this issue will be done for 0.92. For 0.92, lets up default region size from 256M to 1G and talk up pre-split on table creation in manual. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4374) Up default regions size from 256M to 1G
[ https://issues.apache.org/jira/browse/HBASE-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13134729#comment-13134729 ] stack commented on HBASE-4374: -- Committed to branch and trunk. Up default regions size from 256M to 1G --- Key: HBASE-4374 URL: https://issues.apache.org/jira/browse/HBASE-4374 Project: HBase Issue Type: Task Reporter: stack Priority: Blocker Fix For: 0.92.0 Attachments: 4374.txt HBASE-4365 has some discussion of why we default for a table should tend to fewer bigger regions. It doesn't look like this issue will be done for 0.92. For 0.92, lets up default region size from 256M to 1G and talk up pre-split on table creation in manual. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4374) Up default regions size from 256M to 1G
[ https://issues.apache.org/jira/browse/HBASE-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13127829#comment-13127829 ] Jean-Daniel Cryans commented on HBASE-4374: --- bq. In old days there used to be an optimal balance to be struck between flush size, compaction size and region split size. IMO something that radically screws this up is compression. I've been experimenting with 2GB memstore flush size on a LZO'd table and saw radically better write performance. I think it would be good that we bring the flush size up as we bring up the split size, since this means less regions per RS leaving room for bigger and more efficient Memstores. Up default regions size from 256M to 1G --- Key: HBASE-4374 URL: https://issues.apache.org/jira/browse/HBASE-4374 Project: HBase Issue Type: Task Reporter: stack Priority: Blocker Fix For: 0.92.0 HBASE-4365 has some discussion of why we default for a table should tend to fewer bigger regions. It doesn't look like this issue will be done for 0.92. For 0.92, lets up default region size from 256M to 1G and talk up pre-split on table creation in manual. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4374) Up default regions size from 256M to 1G
[ https://issues.apache.org/jira/browse/HBASE-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13103397#comment-13103397 ] Andrew Purtell commented on HBASE-4374: --- If we can get online schema edits into 0.92, at least metadata like HTD/HCD attributes, then users can easily change the split points as tables grow. Can add a ruby script helper for this purpose in bin or shell support. Does not take away from talking up presplitting but provides a good alternative if presplitting is not an option for whatever reason (e.g. keyspace distribution not well known). Up default regions size from 256M to 1G --- Key: HBASE-4374 URL: https://issues.apache.org/jira/browse/HBASE-4374 Project: HBase Issue Type: Task Reporter: stack Priority: Blocker Fix For: 0.92.0 HBASE-4365 has some discussion of why we default for a table should tend to fewer bigger regions. It doesn't look like this issue will be done for 0.92. For 0.92, lets up default region size from 256M to 1G and talk up pre-split on table creation in manual. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
