I think you are confusing the "current cluster topology" and the "baseline topology" terms. Baseline topology cannot contain client nodes. Current baseline topology can be printed or changed by "control.sh" script. You can read more about baseline topology here: [1]
[1]: https://apacheignite.readme.io/docs/baseline-topology вт, 21 авг. 2018 г. в 19:40, scottmf <[email protected]>: > Hi Alex, Yes, the baseline topology contains both the server nodes and the > client node. Everything is looks as I would expect including the IP > addresses. > > A couple more notes: > > - when the nodes get restarted the IP addresses will disappear from > the baseline topology, then will come back. The IP address may change when > it comes back but the filesystem will still be intact. > - once the second node is back up the cache comes back as well, > meaning that the client can successfully query it again. The client is not > able to query the cache while the first node is down when this exception > occurs. I'm confused how that could be the case. I even experimented with > changing my cache to be simply REPLICATED, rather than PARTITIONED, with > backups > 1 > - in my igniteConfiguration I do set the number of threads in the > public and system thread pools to 2 and the rebalance pool size to 1 as > this is a simple dev setup Any idea? > ------------------------------ > Sent from the Apache Ignite Users mailing list archive > <http://apache-ignite-users.70518.x6.nabble.com/> at Nabble.com. > >
