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 2017/09/26 12:18:00 UTC

[jira] [Updated] (IGNITE-4675) Make client node to fetch configuration from server (i.e. connect only by address:port)

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

Vladimir Ozerov updated IGNITE-4675:
------------------------------------
    Fix Version/s:     (was: 2.3)

> Make client node to fetch configuration from server (i.e. connect only by address:port)
> ---------------------------------------------------------------------------------------
>
>                 Key: IGNITE-4675
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4675
>             Project: Ignite
>          Issue Type: Improvement
>          Components: general
>            Reporter: Yakov Zhdanov
>
> Now we need pretty verbose configuration for client to connect to the server topology.
> What if we add the very first step to our start procedure that will make client to connect to provided server's discovery and fetch the configuration and after that continue with ordinary start. This makes possible for client to connect having only address and port.
> So, we add Ignition.start(String address, int port); - the simplest overload
> One of the problem I see - server topology completely changes after client fetches and configuration becomes invalid for current server. In this case we can refetch - just put a loop to the new method.
> New method should also honor SSL settings, any stuff added by plugins, e.g. security.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)