[jira] [Commented] (IGNITE-27522) .NET: handle multiple endpoints for the same node

[Pavel Tupitsyn (Jira)]

    [ 
https://issues.apache.org/jira/browse/IGNITE-27522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18050802#comment-18050802
 ] 

Pavel Tupitsyn commented on IGNITE-27522:
-----------------------------------------

Example
{code}
    public async Task TestDuplicateEndpoints()
    {
        // TODO: Check what happens in Java
        using var server = new FakeServer
        {
            AllowMultipleConnections = true
        };

        using var logger = new ConsoleLogger(LogLevel.Trace);

        var cfg = new IgniteClientConfiguration($"127.0.0.1:{server.Port}", 
$"localhost:{server.Port}")
        {
            LoggerFactory = logger
        };

        using var client = await IgniteClient.StartAsync(cfg);
        var tables = await client.Tables.GetTablesAsync();
        Assert.NotNull(tables);

        await Task.Delay(500);
        Assert.AreEqual(1, client.GetConnections().Count);
    }
{code}

> .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: platforms ai3, 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)