hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18086) Create native client which creates load on selected cluster
Date Wed, 19 Jul 2017 17:10:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16093423#comment-16093423

Ted Yu commented on HBASE-18086:

Currently load-client performs both scan and get for the verification phase.
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.

I choose to keep the naming for these two options:
+DEFINE_bool(skip_get, false, "skip get / scan");
+DEFINE_bool(skip_put, false, "skip put's");
In simple-client, the counterparts are named gets / puts. However, I think skip_get is more
intuitive - the flag is used to skip some action.
The default values for these options convey the same result.

w.r.t. PrefixZero(), I don't see impact on performance for the current version. So I kept

DoGet() may use reversed string for verification conditionally. That is why I prefer separate
methods for scan and get.

w.r.t. letting multi-get requests go to different regions, in patch v16 iteration i would
issue gets for iteration i+2 (scans and gets are interleaved).

> 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

View raw message