[jira] [Created] (HBASE-19371) Running WALPerformanceEvaluation against asyncfswal throws exceptions

stack created HBASE-19371: - Summary: Running WALPerformanceEvaluation against asyncfswal throws exceptions Key: HBASE-19371 URL: https://issues.apache.org/jira/browse/HBASE-19371 Project: HBase

Re: [DISCUSS] hbase-thirdparty versioning

I think it is coincidental in this case, and we actively wouldn't want to peg them. On Tue, Nov 28, 2017 at 6:21 PM, Jerry He wrote: > Is it an intention to use the same version as hbase 2. Or is it just > coincidental, and we can not really peg them? > > On Tue, Nov 28,

Re: [DISCUSS] Performance degradation in master (compared to 2-alpha-1)

I do not mean this is the ONLY problem, and this may not be the problem in your case, but I think it is worth to tell people about the possible reason of performance downgrading right? Thanks. 2017-11-29 11:07 GMT+08:00 Vladimir Rodionov : > >> CompletableFuture more and

Re: [DISCUSS] Performance degradation in master (compared to 2-alpha-1)

>> CompletableFuture more and more in our code base, but at least before >>jdk8u131 there is a performance regression for CompletableFuture. The performance regression is 2x, so this should be something else On Tue, Nov 28, 2017 at 6:49 PM, 宾莉金（binlijin） wrote: >

Re: [DISCUSS] Performance degradation in master (compared to 2-alpha-1)

HBASE-19338 has committed, do you want to update the master branch and test it again? 2017-11-29 10:32 GMT+08:00 张铎(Duo Zhang) : > And one thing may effect performance is that, now we rely on > CompletableFuture more and more in our code base, but at least before >

Re: [DISCUSS] Performance degradation in master (compared to 2-alpha-1)

And one thing may effect performance is that, now we rely on CompletableFuture more and more in our code base, but at least before jdk8u131 there is a performance regression for CompletableFuture. So consider moving to the newest jdk if you are still on an older version. Thanks. 2017-11-29 3:35

[jira] [Resolved] (HBASE-19368) [nightly] Make xml test non-voting in branch-1.2

[ https://issues.apache.org/jira/browse/HBASE-19368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-19368. --- Resolution: Fixed Assignee: stack Hadoop Flags: Reviewed See here how the xml check doesn't

Re: [DISCUSS] hbase-thirdparty versioning

Is it an intention to use the same version as hbase 2. Or is it just coincidental, and we can not really peg them? On Tue, Nov 28, 2017 at 4:08 PM Josh Elser wrote: > > > On 11/28/17 4:54 PM, Stack wrote: > > On Tue, Nov 28, 2017 at 1:14 PM, Mike Drob

Re: [DISCUSS] hbase-thirdparty versioning

On 11/28/17 4:54 PM, Stack wrote: On Tue, Nov 28, 2017 at 1:14 PM, Mike Drob wrote: Wanted to get some input on the versioning scheme for our hbase-thirdparty artifacts. We are moving all of the relocation from o.a.h.shaded to o.a.h.thirdparty due to conflicts with our

[jira] [Created] (HBASE-19370) Replace all uses of RowTooBigException from o.a.h.server with class of same name from o.a.h.client

Andrew Purtell created HBASE-19370: -- Summary: Replace all uses of RowTooBigException from o.a.h.server with class of same name from o.a.h.client Key: HBASE-19370 URL:

[jira] [Created] (HBASE-19369) HBase Should use Builder Pattern to Create Log Files while using WAL on Erasure Coding

Alex Leblang created HBASE-19369: Summary: HBase Should use Builder Pattern to Create Log Files while using WAL on Erasure Coding Key: HBASE-19369 URL: https://issues.apache.org/jira/browse/HBASE-19369

Re: [DISCUSS] hbase-thirdparty versioning

On Tue, Nov 28, 2017 at 1:14 PM, Mike Drob wrote: > Wanted to get some input on the versioning scheme for our hbase-thirdparty > artifacts. > > We are moving all of the relocation from o.a.h.shaded to o.a.h.thirdparty > due to conflicts with our non-thirdparty shaded libraries.

[jira] [Created] (HBASE-19368) [nightly] Make xml test non-voting in branch-1.2

stack created HBASE-19368: - Summary: [nightly] Make xml test non-voting in branch-1.2 Key: HBASE-19368 URL: https://issues.apache.org/jira/browse/HBASE-19368 Project: HBase Issue Type: Sub-task

[DISCUSS] hbase-thirdparty versioning

Wanted to get some input on the versioning scheme for our hbase-thirdparty artifacts. We are moving all of the relocation from o.a.h.shaded to o.a.h.thirdparty due to conflicts with our non-thirdparty shaded libraries. Currently, the next release is slated to be of the thirdparty libs is slated

[jira] [Created] (HBASE-19367) Refactoring in RegionStates, and RSProcedureDispatcher

Appy created HBASE-19367: Summary: Refactoring in RegionStates, and RSProcedureDispatcher Key: HBASE-19367 URL: https://issues.apache.org/jira/browse/HBASE-19367 Project: HBase Issue Type:

[jira] [Resolved] (HBASE-19247) [hbase-thirdparty] upgrade to Netty 4.1.17

[ https://issues.apache.org/jira/browse/HBASE-19247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-19247. --- Resolution: Fixed > [hbase-thirdparty] upgrade to Netty 4.1.17 >

[jira] [Created] (HBASE-19366) Backport to branch-1 HBASE-19035 Miss metrics when coprocessor use region scanner to read data

stack created HBASE-19366: - Summary: Backport to branch-1 HBASE-19035 Miss metrics when coprocessor use region scanner to read data Key: HBASE-19366 URL: https://issues.apache.org/jira/browse/HBASE-19366

[jira] [Created] (HBASE-19365) FSTableDescriptors#get() can return null reference, in some cases, it is not checked

huaxiang sun created HBASE-19365: Summary: FSTableDescriptors#get() can return null reference, in some cases, it is not checked Key: HBASE-19365 URL: https://issues.apache.org/jira/browse/HBASE-19365

Re: [DISCUSS] Performance degradation in master (compared to 2-alpha-1)

Ted, To clarify, I'm talking about a hypothetical bugfix that impacted performance, not to imply that I know of a specific such change. I've seen it often enough before that performance is blazing fast at the expense of accuracy and people are surprised when correctness takes longer. Mike On

Re: [DISCUSS] Performance degradation in master (compared to 2-alpha-1)

Mike: Which JIRA was the important bug-fix ? Thanks On Tue, Nov 28, 2017 at 9:16 AM, Mike Drob wrote: > Eshcar - do you have time to try the other alpha releases and see where > exactly we introduced the regressions? > > Also, I'm worried that the performance regression may

Re: [DISCUSS] Performance degradation in master (compared to 2-alpha-1)

I do not know if this is related, but test suite for backup now runs 57 min on master. It used to run under 34 -Vlad On Tue, Nov 28, 2017 at 9:16 AM, Mike Drob wrote: > Eshcar - do you have time to try the other alpha releases and see where > exactly we introduced the

Re: [DISCUSS] Performance degradation in master (compared to 2-alpha-1)

Eshcar - do you have time to try the other alpha releases and see where exactly we introduced the regressions? Also, I'm worried that the performance regression may be related to an important bug-fix, where before we may have had fast writes but also risked incorrect behavior somehow. Mike On

Re: [DISCUSS] Performance degradation in master (compared to 2-alpha-1)

I agree, so will wait till we focus on performance. Just one more update, I also ran the same experiment (write-only) with banch-2 beta-1.Here is a summary of the throughput I see in each tag/branch: ---  | BASIC | NONE  |

[jira] [Created] (HBASE-19364) Truncate_preserve fails with table when replica region > 1

Pankaj Kumar created HBASE-19364: Summary: Truncate_preserve fails with table when replica region > 1 Key: HBASE-19364 URL: https://issues.apache.org/jira/browse/HBASE-19364 Project: HBase

[jira] [Created] (HBASE-19362) Remove unused imports from hbase-thrift module

Jan Hentschel created HBASE-19362: - Summary: Remove unused imports from hbase-thrift module Key: HBASE-19362 URL: https://issues.apache.org/jira/browse/HBASE-19362 Project: HBase Issue Type:

[jira] [Created] (HBASE-19361) Rename the KeeperException to ReplicationException in ReplicationQueuesClient for abstracting

Zheng Hu created HBASE-19361: Summary: Rename the KeeperException to ReplicationException in ReplicationQueuesClient for abstracting Key: HBASE-19361 URL: https://issues.apache.org/jira/browse/HBASE-19361

[jira] [Created] (HBASE-19360) Remove unused imports from hbase-zookeeper module

Jan Hentschel created HBASE-19360: - Summary: Remove unused imports from hbase-zookeeper module Key: HBASE-19360 URL: https://issues.apache.org/jira/browse/HBASE-19360 Project: HBase Issue

[jira] [Created] (HBASE-19359) Revisit the default config of hbase client retries number

Guanghao Zhang created HBASE-19359: -- Summary: Revisit the default config of hbase client retries number Key: HBASE-19359 URL: https://issues.apache.org/jira/browse/HBASE-19359 Project: HBase