ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amelchev Nikita (Jira)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-12323) Test GridCommandHandlerTest. testBaselineAutoAdjustmentAutoRemoveNode is flaky
Date Fri, 15 Nov 2019 11:07:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-12323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16975014#comment-16975014
] 

Amelchev Nikita edited comment on IGNITE-12323 at 11/15/19 11:06 AM:
---------------------------------------------------------------------

[~alex_pl], could you take a look, please? It seems that Dmitriy cannot take a look.


was (Author: nsamelchev):
[~alexpl], could you take a look, please? It seems that Dmitriy cannot take a look.

> Test GridCommandHandlerTest. testBaselineAutoAdjustmentAutoRemoveNode is flaky
> ------------------------------------------------------------------------------
>
>                 Key: IGNITE-12323
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12323
>             Project: Ignite
>          Issue Type: Test
>            Reporter: Amelchev Nikita
>            Assignee: Amelchev Nikita
>            Priority: Minor
>             Fix For: 2.8
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Test {{GridCommandHandlerTest. testBaselineAutoAdjustmentAutoRemoveNode}} is flaky.
> The reason is that node stopping may be more than the auto adjust timeout. This cause
assertion error on topology size check:
> {code:java}
>         assertEquals(EXIT_CODE_OK, execute("--baseline", "auto_adjust", "enable", "timeout",
"2000"));
>         assertEquals(3, ignite.cluster().currentBaselineTopology().size());
>         stopGrid(2); // May be more than 2 seconds
>         assertEquals(3, ignite.cluster().currentBaselineTopology().size()); // Fails.
> {code}



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

Mime
View raw message