[
https://issues.apache.org/jira/browse/IGNITE-17217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Pavlov updated IGNITE-17217:
-----------------------------------
Release Note: Java thin: Fixed an issue that caused addresses not to be
reloaded from ClientAddressFinder on connection loss in Kubernetes. (was: Java
thin: reload addresses from ClientAddressFinder on connection loss to handle
changing server address in Kubernetes and other scenarios.)
> Java thin: addresses are not reloaded from ClientAddressFinder on connection
> loss
> ---------------------------------------------------------------------------------
>
> Key: IGNITE-17217
> URL: https://issues.apache.org/jira/browse/IGNITE-17217
> Project: Ignite
> Issue Type: Bug
> Components: thin client
> Reporter: Pavel Tupitsyn
> Assignee: wkhappy
> Priority: Major
> Fix For: 2.14
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> When all node connections are lost, *ClientAddressFinder.getAddresses* is not
> called to refresh the list of known endpoints.
> For example, when a Kubernetes pod restarts, it may have a different address.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
