ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Pereslegin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9858) [Test Failed] SystemCacheNotConfiguredTest#test flaky fails on TC (timeout).
Date Fri, 09 Nov 2018 14:17:00 GMT

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

Pavel Pereslegin commented on IGNITE-9858:

I also investigated the possibility of removing check in TcpDiscoveryIpFinderAdapter#initializeLocalAddresses
(option 2), but faced with the fact that TcpDiscoverySpi replaces port 0 with default port
47500 ([code link|https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/TcpDiscoverySpi.java#L1901])
and in this case the client can connect to another cluster (IGFS tests reproduce this problem).
I also tried to skip this replacement [here|https://github.com/apache/ignite/pull/5246/files#diff-7a68a14bf6d0ee82769328166d58a34cR1902],
but this is not an obvious change, and I found at least one test failure (TcpDiscoveryVmIpFinderSelfTest.testUnregistration)
with such changes. So I decided to go the other way.

> [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
instance (see {{TcpDiscoveryIpFinderAdapter#initializeLocalAddresses}}).
> 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