You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2025/11/14 08:23:00 UTC

[jira] [Updated] (IGNITE-26909) Thin client optimizations for MultiDC

     [ https://issues.apache.org/jira/browse/IGNITE-26909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Plekhanov updated IGNITE-26909:
---------------------------------------
    Labels: IEP-140 ise  (was: IEP-140)

> Thin client optimizations for MultiDC
> -------------------------------------
>
>                 Key: IGNITE-26909
>                 URL: https://issues.apache.org/jira/browse/IGNITE-26909
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Sergey Chugunov
>            Priority: Major
>              Labels: IEP-140, ise
>
> Unlike thick clients that have full access to cluster's topology and can choose a router server from the closest datacenter, thin clients only have a list of IP addresses or host names of servers without any information what datacenters what servers belong to.
> An obvious solution would be to force user to sort or filter list of servers in connection string so servers from local datacenter would appear at the beginning of the list.
> But it requires a lot of efforts and not always possible.
> So we need a better alternative - a mechanism capable of performing this type of sorting automatically.
> We would add a new parameter to the connection string - like `local_dc`, but the rest of the process should happen automatically, no additional input from the user should be required.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)