[
https://issues.apache.org/jira/browse/IGNITE-26910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-26910:
---------------------------------------
Description:
StaticNodeFinder can resolve names. When it fails to resolve a name, it logs a
warning, but just proceeds without this name's contribution. It makes sense if
any other names are resolved (or IPs are supplied directly). But if only names
are supplied and none of them can be resolved, this probably indicates an
(infrastructure/configuration) problem. In this case the node should probably
fail to make the problem more visible.
Also, we could add retries to the resolution stage.
was:StaticNodeFinder can resolve names. When it fails to resolve a name, it
logs a warning, but just proceeds without this name's contribution. It makes
sense if any other names are resolved (or IPs are supplied directly). But if
only names are supplied and none of them can be resolved, this probably
indicates an (infrastructure/configuration) problem. In this case the node
should probably fail to make the problem more visible.
> Handle unresolvable names in StaticNodeFinder
> ---------------------------------------------
>
> Key: IGNITE-26910
> URL: https://issues.apache.org/jira/browse/IGNITE-26910
> Project: Ignite
> Issue Type: New Feature
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
>
> StaticNodeFinder can resolve names. When it fails to resolve a name, it logs
> a warning, but just proceeds without this name's contribution. It makes sense
> if any other names are resolved (or IPs are supplied directly). But if only
> names are supplied and none of them can be resolved, this probably indicates
> an (infrastructure/configuration) problem. In this case the node should
> probably fail to make the problem more visible.
> Also, we could add retries to the resolution stage.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
