Hazelcast Kubernetes 警告 未知协议

huangapple go评论96阅读模式
英文:

Hazelcast Kubernetes Warning Unknown Protocol

问题

我之前在使用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: 未知协议: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握手头部检测到,但期望普通协议头。
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());
英文:

I was using Zookeeper Hazelcast discovery but now i have changed it to Hazelcast-Kubernetes. It seems it is working fine but some times it prints warning message like :

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)

and

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)

I could not find any protocol usage like OPT or etc.

What should i do to clear this warning ?

Note :

I am using openshift and and my spring boot application use hazelcast distributed cache in 3 pods under one namespace.

Here is my setting :

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());

答案1

得分: 3

这里有一个类似的问题报告在这个GitHub问题页面中。如其所述,在那里添加以下部分可能会解决这个问题:

- containerPort: 5701 

无论如何,这可能是hazelcast-kubernetes的一个错误。请随意将“重现步骤”添加到以下Hazelcast Kubernetes GitHub问题页面中。

英文:

There is a similar issue report in this GH Issue. As described there, adding the following part might solve the issue:

- containerPort: 5701

In any case, it might be a bug of hazelcast-kubernetes. Feel free to add the "steps to reproduce" to the following Hazelcast Kubernetes GH Issue.

huangapple
  • 本文由 发表于 2020年10月16日 19:59:30
  • 转载请务必保留本文链接:https://go.coder-hub.com/64388790.html
匿名

发表评论

匿名网友

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen:

确定