hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12335) IntegrationTestRegionReplicaPerf is flaky
Date Thu, 30 Oct 2014 01:06:35 GMT

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

Nick Dimiduk commented on HBASE-12335:

Which is to say, it would be interesting to run this with different values of {{hbase.client.primaryCallTimeout.get}}
to see how it impacts the 99pct. Probably there's a sweet spot where 99pct remains close to
without replicas but we still enjoy the improvement at 3 9's and 4 9's.

> IntegrationTestRegionReplicaPerf is flaky
> -----------------------------------------
>                 Key: HBASE-12335
>                 URL: https://issues.apache.org/jira/browse/HBASE-12335
>             Project: HBase
>          Issue Type: Test
>          Components: test
>    Affects Versions: 0.99.0, 2.0.0
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>             Fix For: 2.0.0, 0.99.2
>         Attachments: HBASE-12335.00-0.99.patch, HBASE-12335.00.patch, HBASE-12335.00.patch,
HBASE-12335.00.patch, HBASE-12335.01-0.99.patch, HBASE-12335.01.patch, HBASE-12335.02.patch
> I find that this test often fails; the assertion that running with read replicas should
complete faster than without is usually false. I need to investigate further as to why this
is the case and how we should tune it.
> In the mean time, I'd like to change the test to assert instead on the average of the
stdev across all the test runs in each category. Meaning, enabling this feature should reduce
the overall latency variance experienced by the client.

This message was sent by Atlassian JIRA

View raw message