[
https://issues.apache.org/jira/browse/HBASE-18086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095266#comment-16095266
]
Ted Yu commented on HBASE-18086:
--------------------------------
bq. Why are we doing Deletes before Append / Increment?
Since Append / Increment is not idempotent, the delete calls were intended to
make successive runs quicker.
Otherwise, truncate_preserve command is involved which takes some time.
I can drop this in the next patch.
The table is created with the following clause:
{code}
SPLITS => ['0', '1', '2', '3', '4', '5', '6', '7', '8', '9']
{code}
With shifted region (along with unshifted region), more than one region is
involved for the multi-get requests.
w.r.t. simplifying verification logic, since integer written thru Increment has
unique format (e.g. \x00\x00\x00\x00\x00\x00\x00\x01), I want to see if there
is suggestion on how to detect that value of a Cell should be interpreted as
integer.
We shouldn't rely on the length of value since string can be 8 bytes long as
well.
> 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)
