You should define separate configurations per cluster. What you did is an invalid configuration. Say you have two different configurations: cluster1.yaml
config and cluster2.yaml
config. Then all the members of cluster1 should start with cluster1.yaml and the ones in cluster2 should use cluster2.yaml. If you need multiple clusters to be aware of each other - e.g being synchronized, consider using WAN Replication.
In that case the configurations will look like:
cluster1.yaml:
hazelcast:
cluster-name: cluster1
network:
join:
tcp-ip:
enabled: true
member-list:
- A # uses this config
- B # uses this config
cluster2.yaml:
hazelcast:
cluster-name: cluster2
network:
join:
tcp-ip:
enabled: true
member-list:
- C # uses this config
- D # uses this config
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…