[
https://issues.apache.org/jira/browse/IGNITE-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15873888#comment-15873888
]
Valentin Kulichenko commented on IGNITE-2160:
---------------------------------------------
[~vozerov], the biggest problem here is that after client is connected, it can
be disconnected, and then reconnected again. So there are two ways to get a
client in disconnected state, behavior is completely different and user's code
must handle both of them. I just suggested to make this more consistent. Since
user has to implement disconnection handling anyway, why not to use this logic
when client can't connect initially?
Do you have other suggestions on how to make it more usable?
> 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.15#6346)
