RE: The problem after the ignite upgrade
Hi, Clients should be able to connect to the cluster normally. Please share logs if you’re still seeing this. Stan From: hulitao198758 Sent: 27 июля 2018 г. 14:32 To: user@ignite.apache.org Subject: Re: The problem after the ignite upgrade I opened the persistent storage cluster, version 2.3 as long as the boot server and then activate the cluster when the client can be connected directly, after upgrading to 2.6, after activation server cluster for the first time the client connection complains, you then need to Deactive the cluster with clients to connect again later, in an error once, then again to reactivate can connect successful, why? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: The problem after the ignite upgrade
I opened the persistent storage cluster, version 2.3 as long as the boot server and then activate the cluster when the client can be connected directly, after upgrading to 2.6, after activation server cluster for the first time the client connection complains, you then need to Deactive the cluster with clients to connect again later, in an error once, then again to reactivate can connect successful, why? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: The problem after the ignite upgrade
Hi, Could you please provide step by step instruction on how you upgrade the cluster? Please note that in case if you try to use the persistence then the important feature that was added in 8.4 - baseline topology. A baseline topology is a set of Ignite server nodes intended to store data. The nodes from the baseline topology are not limited in terms of functionality and behave as regular server nodes that act as a container for data and computations in Ignite. It changes the activation process. You can read about it here: https://apacheignite.readme.io/docs/baseline-topology BR, Andrei -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
The problem after the ignite upgrade
The problem with the Ignite version upgrading from 2.3 to 2.6 is that when the Server side starts up, the client will report an error when connecting to the Server side. The client must first stop activating the Server side, then connect with the client once, and then reactivate the Server side before the client can connect properly. Why? Is this a BUG -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
