[
https://issues.apache.org/jira/browse/HBASE-18086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095141#comment-16095141
]
Devaraj Das commented on HBASE-18086:
-------------------------------------
bq. Since load-client is supposed to verify large amount of data, I think it
makes more sense to adopt this approach instead of issuing scan and get in two
rounds of verification.
The idea is to put "stress" in the various code path. Let's get the behavior
where one can say what to use via an option - scan or get or multi-get. By
default it can do scan or multi-get...
> Create native client which creates load on selected cluster
> -----------------------------------------------------------
>
> Key: HBASE-18086
> URL: https://issues.apache.org/jira/browse/HBASE-18086
> Project: HBase
> Issue Type: Sub-task
> Reporter: Ted Yu
> Assignee: Ted Yu
> Attachments: 18086.v11.txt, 18086.v12.txt, 18086.v14.txt,
> 18086.v17.txt, 18086.v1.txt, 18086.v3.txt, 18086.v4.txt, 18086.v5.txt,
> 18086.v6.txt, 18086.v7.txt, 18086.v8.txt
>
>
> This task is to create a client which uses multiple threads to conduct Puts
> followed by Gets against selected cluster.
> Default is to run the tool against local cluster.
> This would give us some idea on the characteristics of native client in terms
> of handling high load.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
