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 Pereslegin (Jira)" <ji...@apache.org> on 2025/08/11 16:30:00 UTC

[jira] [Updated] (IGNITE-26005) Thin 3.0. Improve connection hostname resolution

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

Pavel Pereslegin updated IGNITE-26005:
--------------------------------------
    Description: 
At the moment Java thin client assumes that one hostname should be resolved to one IP.

But we need to support the following cases:

* Single DNS name with multiple A records (all returned together)
* Single DNS name with round-robin A record (each resolution returns a different A record)

Note:  It is also worth expanding the current documentation and describe recommended setups for multinode connection (including setup for kubernetes headless service (DNS names with multiple A records)) 


  was:
At the moment Java thin client assumes that one hostname should be resolved to one IP.

But we need to support the following cases:

* Single DNS name with multiple A records (all returned together)
* Single DNS name with round-robin A record (each resolution returns a different A record)



> Thin 3.0. Improve connection hostname resolution
> ------------------------------------------------
>
>                 Key: IGNITE-26005
>                 URL: https://issues.apache.org/jira/browse/IGNITE-26005
>             Project: Ignite
>          Issue Type: Improvement
>          Components: thin clients ai3
>    Affects Versions: 3.0
>            Reporter: Pavel Pereslegin
>            Priority: Major
>              Labels: ignite-3
>
> At the moment Java thin client assumes that one hostname should be resolved to one IP.
> But we need to support the following cases:
> * Single DNS name with multiple A records (all returned together)
> * Single DNS name with round-robin A record (each resolution returns a different A record)
> Note:  It is also worth expanding the current documentation and describe recommended setups for multinode connection (including setup for kubernetes headless service (DNS names with multiple A records)) 



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