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

Mikhail Antonov commented on HBASE-16101:
-----------------------------------------

[~mbertozzi] [~appy] guys please ping me before commits to 1.3.0, as I'm 
stabilizing branch now, as I posted here - 
http://mail-archives.apache.org/mod_mbox/hbase-dev/201608.mbox/%3CCAHxLZBUVM7L9Bfi8xhVs7PYZLB%3DN5qxefY9zhTqEZovk5StvLg%40mail.gmail.com%3E

Let's also target such jiras to 1.3.1 now.



> Procedure v2 - Perf Tool for WAL
> --------------------------------
>
>                 Key: HBASE-16101
>                 URL: https://issues.apache.org/jira/browse/HBASE-16101
>             Project: HBase
>          Issue Type: Sub-task
>          Components: proc-v2, tooling
>            Reporter: Appy
>            Assignee: Appy
>             Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3
>
>         Attachments: HBASE-16101.master.001.patch, 
> HBASE-16101.master.002.patch, HBASE-16101.master.003.patch, 
> HBASE-16101.master.004.patch, HBASE-16101.master.005.patch, 
> HBASE-16101.master.006.patch, HBASE-16101.master.007.patch, 
> HBASE-16101.master.008.patch, HBASE-16101.master.009.patch, 
> HBASE-16101.master.010.patch
>
>
> Add upstream tools to measure procedure perf 
> There are 2 main thing to measure:
> - Procedure Loading
> - Procedure Writing



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to