[
https://issues.apache.org/jira/browse/HBASE-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-5401:
-------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Release Note: Changes how many tasks PE runs when clients are mapreduce.
Now tasks == client count. Previous we hardcoded ten tasks per client instance.
Status: Resolved (was: Patch Available)
Pushed. Makes sense. This baffled you and Oliver. Thats enough. Thanks for the
patch [~easyliangjob]
> PerformanceEvaluation generates 10x the number of expected mappers
> ------------------------------------------------------------------
>
> Key: HBASE-5401
> URL: https://issues.apache.org/jira/browse/HBASE-5401
> Project: HBase
> Issue Type: Bug
> Components: test
> Affects Versions: 2.0.0
> Reporter: Oliver Meyn
> Assignee: Yi Liang
> Fix For: 2.0.0
>
> Attachments: HBASE-5401-V1.patch
>
>
> With a command line like 'hbase org.apache.hadoop.hbase.PerformanceEvaluation
> randomWrite 10' there are 100 mappers spawned, rather than the expected 10.
> The culprit appears to be the outer loop in writeInputFile which sets up 10
> splits for every "asked-for client". I think the fix is just to remove that
> outer loop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
