You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2022/12/08 10:45:00 UTC
[jira] [Updated] (IGNITE-18147) CLI hangs on slow dns resolution
[ https://issues.apache.org/jira/browse/IGNITE-18147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Puchkovskiy updated IGNITE-18147:
---------------------------------------
Reviewer: Roman Puchkovskiy
> CLI hangs on slow dns resolution
> --------------------------------
>
> Key: IGNITE-18147
> URL: https://issues.apache.org/jira/browse/IGNITE-18147
> Project: Ignite
> Issue Type: Task
> Components: cli, rest
> Reporter: Aleksandr
> Assignee: Aleksandr
> Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Micronaut goes to the Internet at the start. In case there is no internet on the machine it uses some fall-back logic. We have to force micronaut to use this logic by default because there is no reason to go to the Internet for the CLI application.
> The same should be done for REST Component.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)