Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.13
-
None
-
Fixed node resolving stale addresses from previously restarted and killed nodes
-
Release Notes Required
Description
Observation: Ignite tries to resolve all known IP and DNS names exposed by the nodes since the cluster startup. This might cause a delay in response if DNS resolution takes some time and critical for Kubernetes envroments.
The issue is due to the ignite keeping track of the topology history.
Attachments
Issue Links
- links to