处理一个节点(4节点集群)ElasticSearch的客户端http流量时捕获异常

时间:2015-01-14 10:55:31

标签: java apache elasticsearch netty logstash

[2015-01-14 04:14:41,855][WARN ][shield.transport.netty   ] [VMAMNA7P717M5A] Caught exception while handling client http traffic, closing connection [id: 0x77edb16a, /10.168.226.131:52730 => /10.168.226.129:9200]org.elasticsearch.common.netty.handler.ssl.NotSslRecordException: not an SSL/TLS record: 474554202f5f636c75737465722f6865616c746820485454502f312e310d0a4163636570743a206170706c69636174696f6e2f6a736f6e0d0a436f6e74656e742d547970653a206170706c69636174696f6e2f6a736f6e0d0a417574686f72697a6174696f6e3a2042617369632055336c755932466b5955565456334a70644756455a5859365a6d464b4d327379596b4a4b626a46710d0a486f73743a2031302e3136382e3232362e3132393a393230300d0a436f6e6e656374696f6e3a204b6565702d416c6976650d0a0d0a
at org.elasticsearch.common.netty.handler.ssl.SslHandler.decode(SslHandler.java:923)
at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425)
at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303)
at org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
at org.elasticsearch.common.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
at org.elasticsearch.common.netty.handler.ipfilter.IpFilteringHandlerImpl.handleUpstream(IpFilteringHandlerImpl.java:154)
at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)
at org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:268)
at org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:255)
at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108)
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:318)
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)
at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)    

我在一个节点(10.168.226.129)的日志中遇到此异常。 ClusterHealth在clusterhealth API中是绿色的。 群集拓扑: 4个节点集群,ElasticSearch 1.4.0,serverJre1.8.25,用于身份验证和加密。

你能告诉我什么是坏的吗?

1 个答案:

答案 0 :(得分:1)

从异常看起来,远程对等体是纯文本连接而没有tls / ssl。