You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2026/01/09 07:57:00 UTC
[jira] [Updated] (IGNITE-27522) .NET: handle multiple endpoints for the same node
[ https://issues.apache.org/jira/browse/IGNITE-27522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Tupitsyn updated IGNITE-27522:
------------------------------------
Labels: .NET ignite-3 (was: ignite-3)
> .NET: handle multiple endpoints for the same node
> -------------------------------------------------
>
> Key: IGNITE-27522
> URL: https://issues.apache.org/jira/browse/IGNITE-27522
> Project: Ignite
> Issue Type: Improvement
> Components: thin clients ai3
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: .NET, ignite-3
> Fix For: 3.2
>
>
> Multiple different endpoints can point to the same server node (e.g. 127.0.0.1 and 127.0.0.2).
> This is likely a misconfiguration, but we should handle it gracefully.
> * Deduplicate endpoints when possible
> * Log a warning when connection is established but another one exists with the same server name
> * Ensure proper cleanup
--
This message was sent by Atlassian Jira
(v8.20.10#820010)