[
https://issues.apache.org/jira/browse/HBASE-20601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16480597#comment-16480597
]
Hadoop QA commented on HBASE-20601:
-----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 4s{color}
| {color:red} HBASE-20601 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.7.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-20601 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12924116/HBASE-20601.patch |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/12872/console |
| Powered by | Apache Yetus 0.7.0 http://yetus.apache.org |
This message was automatically generated.
> And multiPut support and other miscellaneous to PE
> --------------------------------------------------
>
> Key: HBASE-20601
> URL: https://issues.apache.org/jira/browse/HBASE-20601
> Project: HBase
> Issue Type: Bug
> Components: tooling
> Affects Versions: 2.0.0
> Reporter: Allan Yang
> Assignee: Allan Yang
> Priority: Minor
> Fix For: 2.1.0
>
> Attachments: HBASE-20601.patch
>
>
> Add some useful stuff and some refinement to PE tool
> 1. And multiPut support
> Though we have BufferedMutator, sometimes we need to benchmark batch put in a
> certain number.
> Set --multiPut=number to enable batchput(meanwhile, --autoflush need be set
> to false)
> 2. And Connection Number support
> Before, there is only on parameter to control the connection used by threads.
> oneCon=true means all threads use one connection, false means each thread has
> it own connection.
> When thread number is high and oneCon=false, we noticed high context switch
> frequency in the machine which PE run on, disturbing the benchmark
> results(each connection has its own netty worker threads, 2*CPU IIRC).
> So, added a new parameter conNum to PE. set --conNum=2 means all threads will
> share 2 connections.
> 3. And avg RT and avg TPS/QPS statstic for all threads
> Useful when we want to meansure the total throughtput of the cluster
> 4. Delete some redundant code
> Now RandomWriteTest is inherited from SequentialWrite.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
