[
https://issues.apache.org/jira/browse/HBASE-13319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14379164#comment-14379164
]
Liu Shaohui commented on HBASE-13319:
-------------------------------------
[~ndimiduk]
Sorry to not get what's your meaning of more uniformly?
The magic number 10 may be not consistent with TASKS_PER_CLIENT and no other
places have this problem.
So i replaced a magic number with TASKS_PER_CLIENT
{code}
for (int i = 0; i < TASKS_PER_CLIENT; i++) {
for (int j = 0; j < opts.numClientThreads; j++) {
TestOptions next = new TestOptions(opts);
next.startRow = (j * perClientRows) + (i * (perClientRows/10));
next.perClientRunRows = perClientRows / 10;
String s = MAPPER.writeValueAsString(next);
LOG.info("Client=" + j + ", maptask=" + i + ", input=" + s);
int hash = h.hash(Bytes.toBytes(s));
m.put(hash, s);
}
}
{code}
> Support 64-bits total row number in PerformanceEvaluation
> ---------------------------------------------------------
>
> Key: HBASE-13319
> URL: https://issues.apache.org/jira/browse/HBASE-13319
> Project: HBase
> Issue Type: Improvement
> Components: Performance
> Reporter: Liu Shaohui
> Assignee: Liu Shaohui
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-13319-trunk-v1.diff
>
>
> Currently the total row number in PerformanceEvaluation is 32 bits. It's not
> enough when testing a large hbase cluster using PerformanceEvaluation in
> mapreduce mode.
> Suggestions are welcomed~ Thanks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
