Thanks for answer. After detail testing of this case I found some strange things in service starting. If autoActivation is enabled, then services correct start only after cluster restart. Deactivation and node restart cause cluster activation, but not start services.
I can send reproducing code tomorrow. If it same issue? And question about workaround. If it correct to disable auto activation and duplicate equivalent logic in lifecircle bean. I.e. Check baseline topology and activate and deploy services manualy? Thanks. Отправлено с моего телефона на Windows 10 От: akurbanov Отправлено: 10 мая 2018 г. в 21:31 Кому: [email protected] Тема: Re: Ignite hangs forever on add node Hi, This is a known issue and is already fixed: https://issues.apache.org/jira/browse/IGNITE-8134 After calling cluster.active(true), cluster nodes form baseline topology and currently it's impossible to deploy services from node out of topology on active cluster. Will be available in future Ignite versions. Best regards, Anton -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
