ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maxim Muzafarov <maxmu...@gmail.com>
Subject [IGNITE-7789] Ignite Client Nodes testErrorOnDisconnect()
Date Tue, 27 Feb 2018 12:58:51 GMT
Hi all,

I just briefly look at this issue [1] and found that for:

1) CollectionConfiguration[2] we have default  backup = 0;
2) AtomicConfiguration[3] we have DFLT_BACKUPS = 1;

Is this correct? Because, both of them used for testing
dataStructureOperationsTest(). After disconnet and recreation cache
GridCacheAtomicLongImpl the default value for backup used.

We have doTestIgniteOperationOnDisconnect() and it's argument of operations
List<T2<Callable, C1<Object, Boolean>> which calls asynch. So thats why we
have unstable test-case.

OK - test case
[2018-02-27 15:51:05,065][INFO ][async-callable-runner-1][root] Queue
[2018-02-27 15:51:05,065][INFO ][async-callable-runner-1][root] Set creation
[2018-02-27 15:51:05,065][INFO ][async-callable-runner-1][root] Atomic

FAIL - test case
2018-02-27 15:52:23,304][INFO ][async-callable-runner-1][root] Atomic
[2018-02-27 15:52:23,304][INFO ][async-callable-runner-1][root] Queue
[2018-02-27 15:52:23,303][INFO ][async-callable-runner-1][root] Set creation

Can i take this issue for mysefl?

[1] https://issues.apache.org/jira/browse/IGNITE-7789

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message