I think a proper fix would be to reuse the logic of automatic baseline
change that is planned to be implemented and automatically activate the
cluster after a certain timeout is reached.
Note that immediate cluster activation on first node start won't work
because under concurrent nodes start and
Guys,
We have auto-activation on restart of persistent cluster when last
baseline node joins the cluster. On first start we have no baseline
topology, and thus no auto-activation.
I think it would be useful to add java snippet to Ignite documentation
that will safely activate the cluster on
Vladimir,
Auto-activation on the first start?
Please, shared an issue link if you have.
On Tue, Jun 26, 2018 at 11:29 AM Vladimir Ozerov
wrote:
> Pavel,
>
> As far as I know we agreed to implement auto activation in one of the
> nearest releases. Am I missing something?
>
> вт, 26 июня 2018 г.
Pavel,
As far as I know we agreed to implement auto activation in one of the
nearest releases. Am I missing something?
вт, 26 июня 2018 г. в 0:56, Pavel Kovalenko :
> Igniters,
>
> By the results of the recent Ignite meeting at St. Petersburg I've noticed
> that some of our users getting stuck w