Hi Denis, thanks for your reply. I did some experiment. Seems the non-BLT node only works for PARTITIONED cache mode, but not for REPLICATED. For REPLICATED mode, the non-BLT node startup will stuck without any exception. So this is the design, right?
My cluster holds many semaphore and atomicRef to sync biz logic, therefore I cannot afford any data partition loss. Regards, Johnny Denis Mekhanikov wrote > When you have persistence configured in your cluster, some set of nodes > form a baseline topology (BLT). Those are the nodes that store the data > and > persist it on their disks. > Nodes outside of the BLT can query the data stored on other nodes that are > in the BLT. > Normally nodes are not added to the baseline automatically when they join > the cluster. It requires manual actions or configuration of baseline > auto-adjustment: > https://www.gridgain.com/docs/latest/developers-guide/baseline-topology#baseline-topology-autoadjustment > > You can add the nodes that you want to store and persist the data to the > baseline. Others can work as "compute-only" nodes. > If you want to optimize the work of nodes that are outside of the BLT, > consider using a near cache: > https://www.gridgain.com/docs/latest/developers-guide/near-cache > > More information about the Baseline Topology feature: > https://www.gridgain.com/docs/latest/developers-guide/baseline-topology > > Denis -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
