[
https://issues.apache.org/jira/browse/IGNITE-21642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-21642:
---------------------------------
Description:
A lot of test cannot start in .NET suite
https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunAllTests/7890147?hideProblemsFromDependencies=false&hideTestsFromDependencies=false&expandBuildTestsSection=true&expandCode+Inspection=true&expandBuildProblemsSection=true&expandBuildChangesSection=true&expandBuildDeploymentsSection=false
There reason is because for test purposes we start several nodes, but one of
them cannot finish its start.
It happens in
{{org.apache.ignite.internal.runner.app.PlatformTestNodeRunner#startNodes}}
on the line
{code:java}
List<Ignite> startedNodes =
igniteFutures.stream().map(CompletableFuture::join).collect(toList());
{code}
The reason is that some node haven't received any event from CMG about adding
new nodes in topology, and that leads to the situation that after
https://issues.apache.org/jira/browse/IGNITE-20553 was merged, any node awaits
itself being presented in the local logical topology, but if we have not
received any events about adding nodes (including adding ourself), the start
will hang
was:
A lot of test cannot start in .NET suite
https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunAllTests/7890147?hideProblemsFromDependencies=false&hideTestsFromDependencies=false&expandBuildTestsSection=true&expandCode+Inspection=true&expandBuildProblemsSection=true&expandBuildChangesSection=true&expandBuildDeploymentsSection=false
There reason is because for test reason we start several test, but one of them
cannot finish its start.
It happens in
{{org.apache.ignite.internal.runner.app.PlatformTestNodeRunner#startNodes}}
on the line
{code:java}
List<Ignite> startedNodes =
igniteFutures.stream().map(CompletableFuture::join).collect(toList());
{code}
The reason is that some node haven't received any event from CMG about adding
new nodes in topology, and that leas to the situation that after
https://issues.apache.org/jira/browse/IGNITE-20553 was merged, any node awaits
itself being presented in the local logical topology, but if we have not
received any events about adding nodes (including adding ourself), the start
will hang
> Bug in CMG manager leads to failures in .NET test suite
> --------------------------------------------------------
>
> Key: IGNITE-21642
> URL: https://issues.apache.org/jira/browse/IGNITE-21642
> Project: Ignite
> Issue Type: Bug
> Reporter: Mirza Aliev
> Priority: Major
> Labels: ignite-3
> Attachments: _Test_Run_.NET_Tests_25164.log (1).zip
>
>
> A lot of test cannot start in .NET suite
> https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunAllTests/7890147?hideProblemsFromDependencies=false&hideTestsFromDependencies=false&expandBuildTestsSection=true&expandCode+Inspection=true&expandBuildProblemsSection=true&expandBuildChangesSection=true&expandBuildDeploymentsSection=false
> There reason is because for test purposes we start several nodes, but one of
> them cannot finish its start.
> It happens in
> {{org.apache.ignite.internal.runner.app.PlatformTestNodeRunner#startNodes}}
> on the line
> {code:java}
> List<Ignite> startedNodes =
> igniteFutures.stream().map(CompletableFuture::join).collect(toList());
> {code}
> The reason is that some node haven't received any event from CMG about adding
> new nodes in topology, and that leads to the situation that after
> https://issues.apache.org/jira/browse/IGNITE-20553 was merged, any node
> awaits itself being presented in the local logical topology, but if we have
> not received any events about adding nodes (including adding ourself), the
> start will hang
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
