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

Roman Puchkovskiy commented on IGNITE-26910:
--------------------------------------------

The patch looks good to me

> Handle unresolvable names in StaticNodeFinder
> ---------------------------------------------
>
>                 Key: IGNITE-26910
>                 URL: https://issues.apache.org/jira/browse/IGNITE-26910
>             Project: Ignite
>          Issue Type: Improvement
>    Affects Versions: 3.1
>            Reporter: Roman Puchkovskiy
>            Assignee: Aditya Mukhopadhyay
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.2
>
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> 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)

Reply via email to