[
https://issues.apache.org/jira/browse/GORA-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251665#comment-13251665
]
stack commented on GORA-117:
----------------------------
@Ferdy True. And looking at goraci, it implements Tool. I just tried passing
args on the command line to goraci and it seems to work:
{code}
$ PATH=/export1/stack/hadoop-1.0.2/bin:$PATH ./goraci.sh Verify
-Dhbase.client.scanner.caching=1000
-Dmapred.map.tasks.speculative.execution=false v5 100
{code}
Scan rate goes from 20k/second to 500k/second.
So, there is no issue here? Or maybe we should add a bit of doc on it (Where
would you suggest?)?
I'll send the goraci lads a README patch to add above command-line stuff for
the Verify step at least.
> gora hbase does not have a mechanism to set the caching on a scanner, which
> makes for poor performance on map/reduce jobs
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: GORA-117
> URL: https://issues.apache.org/jira/browse/GORA-117
> Project: Apache Gora
> Issue Type: Bug
> Components: storage-hbase
> Reporter: Eric Newton
> Assignee: stack
>
> goraci runs a map/reduce job over all the data that it generates. The hbase
> storage uses a scanner that doesn't cache rows, which means every fetch
> requires an RPC call. I experimented with
> scan.setCaching(1000);
> and goraci Verify ran about 30x faster.
--
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
