【问题标题】:Hazelcast Kubernetes Warning Unknown ProtocolHazelcast Kubernetes 警告未知协议
【发布时间】:2021-01-30 22:53:57
【问题描述】:

我使用的是 Zookeeper Hazelcast 发现,但现在我已将其更改为 Hazelcast-Kubernetes。它似乎工作正常,但有时它会打印警告消息,例如:

2020-10-16 13:45:27.434  WARN 1 --- [.IO.thread-in-1] com.hazelcast.nio.tcp.TcpIpConnection    : [10.131.6.73]:5701 [dev] [3.12.7] Connection[id=6, /10.131.6.73:5701->/10.131.6.1:58546, qualifier=null, endpoint=null, alive=false, type=NONE] closed. Reason: Exception in Connection[id=6, /10.131.6.73:5701->/10.131.6.1:58546, qualifier=null, endpoint=null, alive=true, type=NONE], thread=hz.switch-data-analytics.IO.thread-in-1

java.lang.IllegalStateException: Unknown protocol: OPT
             at com.hazelcast.nio.tcp.UnifiedProtocolDecoder.onRead(UnifiedProtocolDecoder.java:107)
             at com.hazelcast.internal.networking.nio.NioInboundPipeline.process(NioInboundPipeline.java:135)
             at com.hazelcast.internal.networking.nio.NioThread.processSelectionKey(NioThread.java:369)
             at com.hazelcast.internal.networking.nio.NioThread.processSelectionKeys(NioThread.java:354)
             at com.hazelcast.internal.networking.nio.NioThread.selectLoop(NioThread.java:280)
             at com.hazelcast.internal.networking.nio.NioThread.run(NioThread.java:235)

2020-10-16 13:45:27.438  WARN 1 --- [.IO.thread-in-2] com.hazelcast.nio.tcp.TcpIpConnection    : [10.131.6.73]:5701 [dev] [3.12.7] Connection[id=7, /10.131.6.73:5701->/10.131.6.1:58548, qualifier=null, endpoint=null, alive=false, type=NONE] closed. Reason: Exception in Connection[id=7, /10.131.6.73:5701->/10.131.6.1:58548, qualifier=null, endpoint=null, alive=true, type=NONE], thread=hz.switch-data-analytics.IO.thread-in-2

java.lang.IllegalStateException: TLS handshake header detected, but plain protocol header was expected.
             at com.hazelcast.nio.tcp.UnifiedProtocolDecoder.loadProtocol(UnifiedProtocolDecoder.java:125)
             at com.hazelcast.nio.tcp.UnifiedProtocolDecoder.onRead(UnifiedProtocolDecoder.java:87)
             at com.hazelcast.internal.networking.nio.NioInboundPipeline.process(NioInboundPipeline.java:135)
             at com.hazelcast.internal.networking.nio.NioThread.processSelectionKey(NioThread.java:369)
             at com.hazelcast.internal.networking.nio.NioThread.processSelectionKeys(NioThread.java:354)
             at com.hazelcast.internal.networking.nio.NioThread.selectLoop(NioThread.java:280)
             at com.hazelcast.internal.networking.nio.NioThread.run(NioThread.java:235)

我找不到任何协议用法,如 OPT 等。

我应该怎么做才能清除这个警告?

注意:

我正在使用 openshift,并且我的 Spring Boot 应用程序在一个命名空间下的 3 个 Pod 中使用 hazelcast 分布式缓存。

这是我的设置:

config.getNetworkConfig().getJoin().getMulticastConfig().setEnabled(false);
config.getNetworkConfig().getJoin().getAwsConfig().setEnabled(false);
config.getNetworkConfig().getJoin().getTcpIpConfig().setEnabled(false);
        config.getNetworkConfig().getJoin().getKubernetesConfig().setEnabled(true)
            .setProperty("service-name", applicationProperties.getHazelcast().getServiceName())
            .setProperty("namespace", applicationProperties.getPod().getNamespace());

【问题讨论】:

    标签: java spring-boot kubernetes openshift hazelcast


    【解决方案1】:

    GH Issue 中有类似的问题报告。如那里所述,添加以下部分可能会解决问题:

    - containerPort: 5701
    

    无论如何,这可能是hazelcast-kubernetes 的错误。随意将“重现的步骤”添加到以下Hazelcast Kubernetes GH Issue

    【讨论】:

    • 您好 Rafal,我会尝试并提供反馈意见
    猜你喜欢
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2018-01-14
    • 1970-01-01
    • 2023-03-31
    • 1970-01-01
    • 1970-01-01
    相关资源
    最近更新 更多