You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Guanghao Zhang (Jira)" <ji...@apache.org> on 2020/08/26 03:34:00 UTC

[jira] [Updated] (HBASE-24035) [Flakey Tests] Disable TestClusterScopeQuotaThrottle#testUserNamespaceClusterScopeQuota

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

Guanghao Zhang updated HBASE-24035:
-----------------------------------
    Fix Version/s: 2.2.6

> [Flakey Tests] Disable TestClusterScopeQuotaThrottle#testUserNamespaceClusterScopeQuota
> ---------------------------------------------------------------------------------------
>
>                 Key: HBASE-24035
>                 URL: https://issues.apache.org/jira/browse/HBASE-24035
>             Project: HBase
>          Issue Type: Test
>            Reporter: Michael Stack
>            Assignee: Michael Stack
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.6
>
>
> testUserNamespaceClusterScopeQuota in TestClusterScopeQuotaThrottle is just spewing:
> {code}
> 2020-03-23 13:33:23,996 INFO  [Listener at localhost/50281] hbase.ChoreService(157): Chore ScheduledChore name=QuotaRefresherChore, period=1800000, unit=MILLISECONDS is enabled.
> 2020-03-23 13:33:25,000 INFO  [Listener at localhost/50281] hbase.ChoreService(157): Chore ScheduledChore name=QuotaRefresherChore, period=1800000, unit=MILLISECONDS is enabled.
> 2020-03-23 13:33:26,002 INFO  [Listener at localhost/50281] hbase.ChoreService(157): Chore ScheduledChore name=QuotaRefresherChore, period=1800000, unit=MILLISECONDS is enabled.
> 2020-03-23 13:33:27,003 INFO  [Listener at localhost/50281] hbase.ChoreService(157): Chore ScheduledChore name=QuotaRefresherChore, period=1800000, unit=MILLISECONDS is enabled.
> {code}
> If I run it standalone it passes. Fails in nightly currently.
> Rather than spend time on this, disabling for now. It came in a good while ago as part of HBASE-21820



--
This message was sent by Atlassian Jira
(v8.3.4#803005)