You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Semen Boikov (JIRA)" <ji...@apache.org> on 2015/06/30 11:45:04 UTC

[jira] [Assigned] (IGNITE-1064) Nodes do not start when multicast IP finder is used (default) and multicast is disabled

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

Semen Boikov reassigned IGNITE-1064:
------------------------------------

    Assignee: Sergey Kozlov  (was: Yakov Zhdanov)

Sergey,

I implemented fix so that it should be possible to start node with default config even if multicast initialization fails. Could you please test with disabled network on windows, linux and mac (branch ignite-1064).

Thanks

> Nodes do not start when multicast IP finder is used (default) and multicast is disabled
> ---------------------------------------------------------------------------------------
>
>                 Key: IGNITE-1064
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1064
>             Project: Ignite
>          Issue Type: Improvement
>          Components: general
>            Reporter: Alexey Goncharuk
>            Assignee: Sergey Kozlov
>            Priority: Blocker
>             Fix For: sprint-7
>
>
> Currently multicast IP finder is used as a default IP finder for Ignite. In a case when network is not available or multicast is disabled the node won't start up with default configuration which is a sever usability issue.



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