[
https://issues.apache.org/jira/browse/HBASE-19867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341891#comment-16341891
]
Appy commented on HBASE-19867:
------------------------------
bq. We need to add a rule explicitly to enforce the timeout? I used to think it
is enabled by default...
I am pretty sure. But confirm jic....
bq. Add a timeout rule in BalancerTestBase so it will work for all sub
classes(I guess). Remove the explicit timeout setting after the Test annotation.
It wont, BalancerTestBase class has no annotation, and CategoryBasedTimeout
builds the timeout using annotation.
Also, going that way, the test type BalancerTestBase would get applied to all
sub-class tests. It won't be possible to make them different, say one medium
and another large.
bq. And for TestStochasticLoadBalancer2, agree, but I think we can do it later.
It does not cause our build failing for now
Makes sense
> Split TestStochasticLoadBalancer into several small tests
> ---------------------------------------------------------
>
> Key: HBASE-19867
> URL: https://issues.apache.org/jira/browse/HBASE-19867
> Project: HBase
> Issue Type: Sub-task
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 2.0.0-beta-2
>
> Attachments: HBASE-19867-v1.patch, image-2018-01-26-12-56-49-560.png
>
>
> Just like what I have done to TestHCM.
> The test is CPU bound. We set a very large number of regions and also a very
> large number iterations which makes some of the tests execute for a very long
> time. It even make things worse that, our machines to run the jenkins job are
> very weak, so it will take much longer time than running them locally...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
