[
https://issues.apache.org/jira/browse/IGNITE-17414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-17414:
----------------------------------
Release Note: Fixed an issue that caused a node is trying to resolve its
hostname if IP is configured with IGNITE_LOCAL_HOST.
> A node is trying to resolve its DNS even if raw IP is configured in
> IGNITE_LOCAL_HOST
> -------------------------------------------------------------------------------------
>
> Key: IGNITE-17414
> URL: https://issues.apache.org/jira/browse/IGNITE-17414
> Project: Ignite
> Issue Type: Bug
> Components: networking
> Affects Versions: 2.13
> Reporter: Semyon Danilov
> Assignee: Semyon Danilov
> Priority: Major
> Fix For: 2.14
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Scenario:
> Given the following etc/hosts from a Kubernetes POD:
> 127.0.0.1 localhost
> ::1 localhost ip6-localhost ip6-loopback
> fe00::0 ip6-localnet
> fe00::0 ip6-mcastprefix
> fe00::1 ip6-allnodes
> fe00::2 ip6-allrouters
> 10.1.2.108 apache-ignite-cluster-2-client-1-0
> And ENV variable IGNITE_LOCAL_HOST=10.1.2.108, we are still resolving this as
> apache-ignite-cluster-2-client-1-0/10.1.2.108
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
