Does Apache Ignite supports PartitionAwareness in scaling cluster?

Question

I am testing Apache Ignite cluster using .NET thin client. I've launched 3 ignite instances on local machine using dotnet launcher ("platforms\dotnet\bin\Apache.Ignite.exe"). The instances found each other and took 10800, 10801, 10802 ports automatically. In my test application I create 100 caches with 1000 records in each cache and then try to get elements from caches sequentally. The problem is that client makes requests to different nodes only if I specify 3 adresses manually "127.0.0.1:10800..10801".

        var configuration = new Core.Client.IgniteClientConfiguration
        {
            Endpoints = new List<string> { "127.0.0.1:10800..10802" },
            EnablePartitionAwareness = true
        };

If I specify "127.0.0.1" or "127.0.0.1:10800" request I made to only one node.

            var configuration = new Core.Client.IgniteClientConfiguration
        {
            Endpoints = new List<string> { "127.0.0.1:10801" },
            EnablePartitionAwareness = true
        };

I've checked client requests with WireShark:

Can I specify only one node if I want to use PartitionAwareness feature?

Can thin client discover other nodes automatically?

We plan to autoscale application depending on memory used, so all node adresses and ports will not be known at client startup.

Alexandr Shapkin Alexandr Shapkin · Accepted Answer · 2020-07-10T14:15:00

Right now it's required to list all addresses for your connection string.

There is an upcoming Thin client discovery feature, that will track the topology changes and save the snapshot on a client-side. Implementation details: https://cwiki.apache.org/confluence/display/IGNITE/IEP-44%3A+Thin+client+cluster+discovery

According to the ticket, the target release is 2.9. I think, the target date is somewhere in September.

Does Apache Ignite supports PartitionAwareness in scaling cluster?

3 Answers