Mule 集群错误：集群配置无效：节点无法启动

Question

我将稍微解释一下我们遇到问题的架构，我们在 AWS 中有一个集群，有 2 个服务器，一个是主服务器，另一个是本地版本 4.3（两台服务器都在 AWS 中运行）和 JVM 11.0 的副本。 12，但我不知道为什么这几天从属实例失败，Mule 运行时出现“断开连接”状态，我决定进入服务器检查，我在 mule 日志中发现以下消息：A Fatal error服务器运行时发生：

*
* Invalid cluster configuration: Node failed to start!                         *
* (java.lang.RuntimeException)                    

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.hazelcast.internal.networking.nio.SelectorOptimizer (file:hazelcast-3.12.jar) to field sun.nio.ch.SelectorImpl.selectedKeys
WARNING: Please consider reporting this to the maintainers of com.hazelcast.internal.networking.nio.SelectorOptimizer
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
DEBUG 2022-12-07 18:43:31,509 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.mule.runtime.module.cluster.internal.HazelcastClusterManager: Node failed to start!
java.lang.IllegalStateException: Node failed to start!
    at com.hazelcast.instance.HazelcastInstanceImpl.<init>(HazelcastInstanceImpl.java:138) ~[hazelcast-3.12.jar:3.12]


INFO  2022-12-07 16:07:44,694 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.mule.runtime.module.cluster.internal.config.ClusterConfigLogger: Mule cluster setup properties >>>
INFO  2022-12-07 16:07:44,694 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.mule.runtime.module.cluster.internal.config.ClusterConfigLogger: Cluster id: 12611154
INFO  2022-12-07 16:07:44,694 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.mule.runtime.module.cluster.internal.config.ClusterConfigLogger: Cluster node id: 2
INFO  2022-12-07 16:07:44,694 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.mule.runtime.module.cluster.internal.config.ClusterConfigLogger: Discovery SPI is not enabled.
INFO  2022-12-07 16:07:44,694 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.mule.runtime.module.cluster.internal.config.ClusterConfigLogger: Reading backup data: false
INFO  2022-12-07 16:07:44,694 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.mule.runtime.module.cluster.internal.config.ClusterConfigLogger: Multicast to discover cluster nodes disabled
INFO  2022-12-07 16:07:44,694 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.mule.runtime.module.cluster.internal.config.ClusterConfigLogger: TCP/IP to discover cluster nodes enabled
INFO  2022-12-07 16:07:44,694 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.mule.runtime.module.cluster.internal.config.ClusterConfigLogger: TCP/IP time to connect 20 seconds
INFO  2022-12-07 16:07:44,694 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.mule.runtime.module.cluster.internal.config.ClusterConfigLogger: TCP/IP discovery members:
INFO  2022-12-07 16:07:44,694 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.mule.runtime.module.cluster.internal.config.ClusterConfigLogger:  - 10.0.3.193
INFO  2022-12-07 16:07:44,694 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.mule.runtime.module.cluster.internal.config.ClusterConfigLogger:  - 10.0.3.84
INFO  2022-12-07 16:07:44,694 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.mule.runtime.module.cluster.internal.config.ClusterConfigLogger: Using port 5701 for inbound connections
INFO  2022-12-07 16:07:44,694 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.mule.runtime.module.cluster.internal.config.ClusterConfigLogger: Inbound request port autoincrement is enabled
INFO  2022-12-07 16:07:44,694 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.mule.runtime.module.cluster.internal.config.ClusterConfigLogger: Using random port for outobund connections
INFO  2022-12-07 16:07:44,694 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.mule.runtime.module.cluster.internal.config.ClusterConfigLogger: No network interface restriction. Using all available interfaces
INFO  2022-12-07 16:07:44,694 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.mule.runtime.module.cluster.internal.config.ClusterConfigLogger: Message backup count: 1
INFO  2022-12-07 16:07:44,710 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.mule.runtime.module.cluster.internal.config.ClusterConfigLogger: Quorum enabled: false
INFO  2022-12-07 16:07:44,710 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.mule.runtime.module.cluster.internal.config.ClusterConfigLogger: Quorum size: 0
INFO  2022-12-07 16:07:44,710 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.mule.runtime.module.cluster.internal.config.ClusterConfigLogger: Mule cluster setup properties <<<
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.hazelcast.internal.networking.nio.SelectorOptimizer (file:/C:/MuleRuntime-Dev/mule/lib/opt/hazelcast-3.12.jar) to field sun.nio.ch.SelectorImpl.selectedKeys
WARNING: Please consider reporting this to the maintainers of com.hazelcast.internal.networking.nio.SelectorOptimizer
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
DEBUG 2022-12-07 16:12:49,744 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.mule.runtime.module.cluster.internal.HazelcastClusterManager: Node failed to start!
java.lang.IllegalStateException: Node failed to start!
    at com.hazelcast.instance.HazelcastInstanceImpl.<init>(HazelcastInstanceImpl.java:138) ~[hazelcast-3.12.jar:3.12]

当我们尝试手动重置服务器或实例时，服务器显示相同的消息我不知道发生了什么，因为没有人改变任何东西。

如果您遇到同样的错误或知道如何解决，能否请您帮助我。

Answer 1

这可能是由于节点之间的连接问题或网络中的某些变化导致一个节点无法访问另一个节点或更改了访问权限（如 IP 更改、端口关闭等）。 另一种可能性是仅在一个节点中更改 Hazelcast 库，但您说您没有进行更改，除非在 Mule 补丁中提供，否则不应更改这些库。

查看日志以了解其他集群错误。 不要注意调试级别的日志。 尝试找出问题所在并修复您的 AWS VPC 中的网络。

警告An illegal reflective access operation has occurred应该与此错误无关。 它在 Mule 4.4.0 中被修复。 当在以前的 Mule 4.x 版本中运行 JDK 11 时会发生这种情况。