You can change the baseline topology ( https://apacheignite.readme.io/docs/baseline-topology) either via control.sh or GridGain web console.
For example, you will see something like this after running "control.sh --baseline": Cluster state: active Current topology version: 5 Baseline nodes: ConsistentID=5de27d47-cef3-4a5d-ac1e-6dfe45156e3f, STATE=ONLINE ConsistentID=7e610021-052c-48ac-8a93-1d1ec2e10fac, STATE=ONLINE -------------------------------------------------------------------------------- Number of baseline nodes: 2 Other nodes: ConsistentID=e019f021-5988-40c0-84fe-d0bb5226c720 Number of other nodes: 1 You can then add node e019f021-5988-40c0-84fe-d0bb5226c720 to your topology via "control.sh --baseline add". On Thu, Dec 20, 2018 at 5:47 AM soonjoin <[email protected]> wrote: > Hi Team, I am testing Ignite on version 2.7.0. I used Ignite native > persistence and cache mode is PARTITIONED. > > I found there’s no data was stored in the node which joined the cluster > after the cluster is already active，even though I deactivate the cluster > and > activate it again. I have to delete the persistent data on all the existing > nodes and restart the cluster, then the new node worked properly. > > Is there any way that I can add a new node to an existing cluster which > Ignite native persistence is enabled without deleting the old persistent > data? > > Thanks a lot. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
