[
https://issues.apache.org/jira/browse/HBASE-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184311#comment-13184311
]
Jean-Daniel Cryans commented on HBASE-4440:
-------------------------------------------
We could show a WARN, but I don't think we would need more than that. In fact,
we could always show a message when the table exists saying something like:
"Using the existing ${tablename} which has ${X} regions".
About the pre-splitting itself, it seems that it creates N+1 regions and the
first one has the end key 0000000000 so it never gets data. Not a biggie, but
could be fixed in another jira.
> add an option to presplit table to PerformanceEvaluation
> --------------------------------------------------------
>
> Key: HBASE-4440
> URL: https://issues.apache.org/jira/browse/HBASE-4440
> Project: HBase
> Issue Type: Improvement
> Components: util
> Reporter: Sujee Maniyam
> Assignee: Sujee Maniyam
> Priority: Minor
> Labels: benchmark
> Fix For: 0.94.0
>
> Attachments: PerformanceEvaluation.java,
> PerformanceEvaluation_HBASE_4440.patch,
> PerformanceEvaluation_HBASE_4440_2.patch
>
>
> PerformanceEvaluation a quick way to 'benchmark' a HBase cluster. The
> current 'write*' operations do not pre-split the table. Pre splitting the
> table will really boost the insert performance.
> It would be nice to have an option to enable pre-splitting table before the
> inserts begin.
> it would look something like:
> (a) hbase ...PerformanceEvaluation --presplit=10 <other options>
> (b) hbase ...PerformanceEvaluation --presplit <other options>
> (b) will try to presplit the table on some default value (say number of
> region servers)
--
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
