ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Goncharuk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9858) [Test Failed] SystemCacheNotConfiguredTest#test flaky fails on TC (timeout).
Date Sat, 27 Oct 2018 14:44:00 GMT

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

Alexey Goncharuk commented on IGNITE-9858:

[~xtern], I believe the behavior you described is not correct because it breaks concurrent
server and client nodes start using shared VM IP finder.
Can you please elaborate how specifically the race between two nodes happen and when the check
for client node is performed?
We should fix this the root cause because many other tests may be affected by the same issue.

> [Test Failed] SystemCacheNotConfiguredTest#test flaky fails on TC (timeout).
> ----------------------------------------------------------------------------
>                 Key: IGNITE-9858
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9858
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.6
>            Reporter: Pavel Pereslegin
>            Assignee: Pavel Pereslegin
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain
>             Fix For: 2.8
> SystemCacheNotConfiguredTest hangs sometimes on TeamCity (timeout).
> Example of such failures on master branch: [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&buildTypeId=&tab=testDetails&testNameId=-2762467041583095183&order=TEST_STATUS_DESC&itemsCount=50&branch_IgniteTests24Java8=%3Cdefault%3E]
> When we using ip finder in shared mode each node should register self address (except
clients, obviously).
> Check that the node is a client uses installed (via DI @IgniteInstanceResource) Ignite
> So when client and server starts simultaneously, the following scenario is possible -
Ignite server injected at first, then the Ignite client injected when the SPI is initialized
({{spiStart}}) both nodes assume that the local node is a client and don't register local
> {noformat}
> [2018-10-11 18:03:49,794][WARN ][tcp-client-disco-msg-worker-#57%client%][TcpDiscoverySpi]
IP finder returned empty addresses list. Please check IP finder configuration. Will retry
every 2000 ms. Change 'reconnectDelay' to configure the frequency of retries.{noformat}

This message was sent by Atlassian JIRA

View raw message