You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/11/17 10:08:58 UTC

[jira] [Updated] (IGNITE-2160) Ignition.start() is blocked if there are no server nodes

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

Vladimir Ozerov updated IGNITE-2160:
------------------------------------
    Fix Version/s:     (was: 1.8)
                   2.0

> Ignition.start() is blocked if there are no server nodes
> --------------------------------------------------------
>
>                 Key: IGNITE-2160
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2160
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Valentin Kulichenko
>            Priority: Critical
>             Fix For: 2.0
>
>
> A node (server or client) should always start without blocking the thread that called {{Ignition.start()}}. Current behavior is confusing and undesirable - e.g., if a node is embedded into web application, the whole application startup process is stuck.
> Additionally, if there are no servers, client node should throw {{IgniteClientDisconnectedException}} on all API calls. It already works this way if all servers leave while client is running.
> @dev list discussion: http://apache-ignite-developers.2346864.n4.nabble.com/Client-connect-quot-hangs-quot-td5765.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)