Use hazelcast to do something wrong. The error log is as follows

com.hazelcast.spi.exception.RetryableHazelcastException: HazelcastInstance is not active!
	at com.hazelcast.spi.impl.NodeEngineImpl.getService(NodeEngineImpl.java:369) ~[hazelcast-3.11.4.jar:3.11.4]
	at com.hazelcast.spi.impl.eventservice.impl.EventServiceImpl.getSegment(EventServiceImpl.java:540) ~[hazelcast-3.11.4.jar:3.11.4]
	at com.hazelcast.spi.impl.eventservice.impl.EventServiceImpl.registerListenerInternal(EventServiceImpl.java:282) ~[hazelcast-3.11.4.jar:3.11.4]
	at com.hazelcast.spi.impl.eventservice.impl.EventServiceImpl.registerLocalListener(EventServiceImpl.java:242) ~[hazelcast-3.11.4.jar:3.11.4]
	at com.hazelcast.internal.cluster.impl.ClusterServiceImpl.addMembershipListener(ClusterServiceImpl.java:790) ~[hazelcast-3.11.4.jar:3.11.4]
	at com.hazelcast.internal.management.ManagementCenterService.<init>(ManagementCenterService.java:141) ~[hazelcast-3.11.4.jar:3.11.4]
	at com.hazelcast.instance.Node.start(Node.java:419) ~[hazelcast-3.11.4.jar:3.11.4]
	at com.hazelcast.instance.HazelcastInstanceImpl.<init>(HazelcastInstanceImpl.java:131) ~[hazelcast-3.11.4.jar:3.11.4]

solutions

Look at the log file carefully

Look at this line carefully

Reason of failure for node join: Joining node's version 3.11.4 is not compatible with cluster version 3.12 (Rolling Member Upgrades are only supported for the next minor version) (Rolling Member Upgrades are only supported in Hazelcast Enterprise)

The versions are not compatible and cannot be upgraded. This means that when upgrading, the whole cluster will restart together, which is intolerable for many websites. It is said that the compatibility of small version will be guaranteed after version 3.1

Modify the dependent version number, repackage and deploy the cluster uniformly. OK, perfect solution