hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-17171) IntegrationTestTimeBoundedRequestsWithRegionReplicas fails with obtuse error when readers have no time to run
Date Wed, 23 Nov 2016 18:28:58 GMT

     [ https://issues.apache.org/jira/browse/HBASE-17171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Josh Elser updated HBASE-17171:
-------------------------------
    Attachment: HBASE-17171.001.patch

.001 The framework sets a configuration property to control how long reads
should be executed. When writes take too long, no time remains for reads
and the user sees an error about a property they must set. We should
prevent this case and log an appropriate message.

Also fixes a rogue character in the class-level javadoc.

> IntegrationTestTimeBoundedRequestsWithRegionReplicas fails with obtuse error when readers
have no time to run
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-17171
>                 URL: https://issues.apache.org/jira/browse/HBASE-17171
>             Project: HBase
>          Issue Type: Bug
>          Components: integration tests
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: HBASE-17171.001.patch
>
>
> Just noticed an odd error message that cropped up in some $dayjob internal testing.
> Sometimes, executions of IntegrationTestTimeBoundedRequestsWithRegionReplicas would result
in an error:
> {noformat}
> Caused by: java.lang.IllegalArgumentException: Please configure hbase.TimeBoundedMultiThreadedReader.runtime
>   at org.apache.hadoop.hbase.test.IntegrationTestTimeBoundedRequestsWithRegionReplicas$TimeBoundedMultiThreadedReader.<init>
> {noformat}
> After digging into the test a bit more, I realized that this is actually failing because
the remaining time left after the writers finish (that is, {{hbase.IntegrationTestTimeBoundedRequestsWithRegionReplicas.runtime}}
minus the time the writers took) was negative. So, the test harness passed a value which always
caused this error.
> We should catch when the time available for the readers is negative and throw an appropriate
error instructing the human to either increase the amount of time for {{hbase.IntegrationTestTimeBoundedRequestsWithRegionReplicas.runtime}}
or decrease the amount of data written.



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

Mime
View raw message