[
https://issues.apache.org/jira/browse/IGNITE-28250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtsev updated IGNITE-28250:
-----------------------------------------
Description: We currently do not specify a listen address when starting a
node in tests. This means that nodes bind to all available interfaces. When
binding to all interfaces we use Java's {{InetAddress.getLocalHost()}} to
identify the local address which will also be advertised to other nodes. This
can be a problem when nodes run in an LXC container, where an external IP is
available, because the external address will be used and advertised, which
means the nodes running in the same container will not communicate through the
much faster loopback interface which may lead to a different test environment
and flaky tests.
> Use loopback IP address as listen address in tests
> --------------------------------------------------
>
> Key: IGNITE-28250
> URL: https://issues.apache.org/jira/browse/IGNITE-28250
> Project: Ignite
> Issue Type: Improvement
> Reporter: Aleksandr Polovtsev
> Assignee: Aleksandr Polovtsev
> Priority: Major
> Labels: ignite-3
>
> We currently do not specify a listen address when starting a node in tests.
> This means that nodes bind to all available interfaces. When binding to all
> interfaces we use Java's {{InetAddress.getLocalHost()}} to identify the local
> address which will also be advertised to other nodes. This can be a problem
> when nodes run in an LXC container, where an external IP is available,
> because the external address will be used and advertised, which means the
> nodes running in the same container will not communicate through the much
> faster loopback interface which may lead to a different test environment and
> flaky tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
