[
https://issues.apache.org/jira/browse/IGNITE-27799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18057748#comment-18057748
]
Roman Puchkovskiy commented on IGNITE-27799:
--------------------------------------------
The patch looks good to me
> Network thread reported as blocked during host name resolution
> --------------------------------------------------------------
>
> Key: IGNITE-27799
> URL: https://issues.apache.org/jira/browse/IGNITE-27799
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksandr Polovtsev
> Assignee: Aleksandr Polovtsev
> Priority: Major
> Labels: ignite-3
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When a node starts it tries to resolve host names provided by the NodeFinder
> and can get stuck (e.g. due to slow DNS). While in this stuck state, it can
> also block incoming connections (see
> {{ConnectionManager.waitForLocalNodeToBeSet}}), since the same thread
> completes the local node future.
> In reality there's no reason for that future to even exist, because the local
> node is known beforehand and this deadlock can safely be eliminated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
