为什么 elasticsearch 获取节点信息失败 org.elasticsearch.action.searc...
\u4e3a\u4ec0\u4e48 elasticsearch \u83b7\u53d6\u8282\u70b9\u4fe1\u606f\u5931\u8d25\u4e3a\u4ec0\u4e48\u6267\u884celasticsearch\u7684api\u4f1a\u51fa\u9519
5.3.3 \u6761\u4ef6\u8fd0\u7b97\u7b26\u548c\u6761\u4ef6\u8868\u8fbe\u5f0f
\u5982\u679c\u5728\u6761\u4ef6\u8bed\u53e5\u4e2d\uff0c\u53ea\u6267\u884c\u5355\u4e2a\u7684\u8d4b\u503c\u8bed\u53e5\u65f6\uff0c \u5e38\u53ef\u4f7f\u7528\u6761\u4ef6\u8868\u8fbe\u5f0f\u6765\u5b9e\u73b0\u3002\u4e0d\u4f46\u4f7f\u7a0b\u5e8f\u7b80\u6d01\uff0c\u4e5f\u63d0\u9ad8\u4e86\u8fd0\u884c\u6548\u7387\u3002
\u6761\u4ef6\u8fd0\u7b97\u7b26\u4e3a?\u548c\uff1a\uff0c\u5b83\u662f\u4e00\u4e2a\u4e09\u76ee\u8fd0\u7b97\u7b26\uff0c\u5373\u6709\u4e09\u4e2a\u53c2\u4e0e\u8fd0\u7b97\u7684\u91cf\u3002
\u7531\u6761\u4ef6\u8fd0\u7b97\u7b26\u7ec4\u6210\u6761\u4ef6\u8868\u8fbe\u5f0f\u7684\u4e00\u822c\u5f62\u5f0f\u4e3a\uff1a
\u8868\u8fbe\u5f0f1? \u8868\u8fbe\u5f0f2\uff1a \u8868\u8fbe\u5f0f3
\u5176\u6c42\u503c\u89c4\u5219\u4e3a\uff1a\u5982\u679c\u8868\u8fbe\u5f0f1\u7684\u503c\u4e3a\u771f\uff0c\u5219\u4ee5\u8868\u8fbe\u5f0f2 \u7684\u503c\u4f5c\u4e3a\u6761\u4ef6\u8868\u8fbe\u5f0f\u7684\u503c\uff0c\u5426\u5219\u4ee5\u8868\u8fbe\u5f0f2\u7684\u503c\u4f5c\u4e3a\u6574\u4e2a\u6761\u4ef6\u8868\u8fbe\u5f0f\u7684\u503c\u3002
\u6761\u4ef6\u8868\u8fbe\u5f0f\u901a\u5e38\u7528\u4e8e\u8d4b\u503c\u8bed\u53e5\u4e4b\u4e2d\u3002
\u4f8b\u5982\u6761\u4ef6\u8bed\u53e5\uff1a
if(a>b) max=a;
else max=b;
\u53ef\u7528\u6761\u4ef6\u8868\u8fbe\u5f0f\u5199\u4e3a
max=(a>b)?a:b;
"size": 50,
"query": {
"filtered": {
"query": {
"bool": {
"must": {
"bool": {
"should": [
{
"match": {
"_all": {
"query": "Happy Pharrel Williams",
"type": "boolean"
}
}
},
{
"flt": {
Node node = NodeBuilder.nodeBuilder().node();
node.start();
但是，如果使用 TransportClient 建立 es 的 Client，方式如下：
TransportClient client = new TransportClient(settings);
client.addTransportAddress(new InetSocketTransportAddress("127.0.0.1", 9300));
这是 ES 2.3 官网上面提供的 TransportClient 方式：https://www.elastic.co/guide/en/elasticsearch/client/java-api/current/transport-client.html
使用 TransportClient 方式，启动程序后，程序可以正常启动，但是控制台一直不停报错，貌似是在一直监测节点，而节点一直没有被发现，所以不停报错，错误信息如下，应用程序控制台错误信息：
2016-05-23 19:40:15.823 INFO 27655 --- [ main] org.elasticsearch.client.transport : [Aliyah Bishop] failed to get node info for [#transport#-1][XXX-MBP.lan][inet[/127.0.0.1:9300]], disconnecting...
org.elasticsearch.transport.RemoteTransportException: Failed to deserialize exception response from stream
Caused by: org.elasticsearch.transport.TransportSerializationException: Failed to deserialize exception response from stream
at org.elasticsearch.transport.netty.MessageChannelHandler.handlerResponseError(MessageChannelHandler.java:173)
at org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:125)
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.channel.Channels.fireMessageReceived(Channels.java:296)
at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462)
at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:443)
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.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:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.StreamCorruptedException: Unsupported version: 1
at org.elasticsearch.common.io.ThrowableObjectInputStream.readStreamHeader(ThrowableObjectInputStream.java:46)
at java.io.ObjectInputStream.<init>(ObjectInputStream.java:299)
at org.elasticsearch.common.io.ThrowableObjectInputStream.<init>(ThrowableObjectInputStream.java:38)
at org.elasticsearch.transport.netty.MessageChannelHandler.handlerResponseError(MessageChannelHandler.java:170)
... 23 common frames omitted
………….
failed to load elasticsearch nodes : org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available: []
es 控制台报错信息：
[2016-05-23 21:45:56,807][WARN ][transport.netty ] [node-1] exception caught on transport layer [[id: 0x8e4b89bc, /127.0.0.1:62566 => /127.0.0.1:9300]], closing connection
java.lang.IllegalStateException: Message not fully read (request) for requestId [233], action [cluster/nodes/info], readerIndex [39] vs expected [57]; resetting
at org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:121)
at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296)
at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462)
at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:443)
at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303)
at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
at org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChannelsHandler.java:75)
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255)
at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)
at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108)
at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)
at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
而且，当我使用嵌入式node启动节点后，系统会自动启动一个node节点，node.name 也是随机的，并且并没有将该节点加入启动的es集群中，我加入的索引和数据也不能出现在 my-cluster 集群中
所以有两个问题：
1、为什么我使用嵌入式node启动节点，启动后的节点不会加入到集群中？
2、使用 TransportClient 方式建立 Client，启动程序后，程序的控制台，和服务器端的es一直报错，获取节点信息失败，是什么原因？即上面的错误信息
下面是环境版本信息：
服务器端 es 版本：2.3.3
jdk 版本：1.7.0_79
spring-data-elasticsearch 版本：1.2.0.RELEASE（即：elasticsearch-1.4.4.jar）
服务器端 es 配置，elasticsearch.yml：
cluster.name: my-cluster
node.name: node-1
http 端口为：9200
节点间的通信端口为：9300
关于第二个问题尝试了很多解决方案，比如：
1、应用 和 es 的 jdk 环境版本不一致。已检查过一致
https://github.com/elastic/elasticsearch/issues/3835
2、es 多个节点之间的JDK版本不一致。我使用的只是单节点，并且都在我本地机器上
http://jontai.me/blog/2013/06/elasticsearch-remotetransportexception-failed-to-deserialize-exception-response-from-stream/
3、idk 版本过低，建议1.7+。已是1.7+
最后附上两种启动节点方式的完整代码
1、嵌入式 node 启动
import org.elasticsearch.client.Client;
import org.elasticsearch.node.Node;
import org.elasticsearch.node.NodeBuilder;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.data.elasticsearch.repository.config.EnableElasticsearchRepositories;
@Configuration
@EnableElasticsearchRepositories(basePackages = "xx.xxx.domain.repository.elastic")
public class ElasticsearchConfiguration {
@Bean
public Client client() {
Node node = NodeBuilder.nodeBuilder().node();
node.start();
return node.client();
}
}
2、TransportClient 方式
import org.elasticsearch.client.Client;
import org.elasticsearch.client.transport.TransportClient;
import org.elasticsearch.common.settings.ImmutableSettings;
import org.elasticsearch.common.settings.Settings;
import org.elasticsearch.common.transport.InetSocketTransportAddress;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.data.elasticsearch.core.ElasticsearchOperations;
import org.springframework.data.elasticsearch.core.ElasticsearchTemplate;
import org.springframework.data.elasticsearch.repository.config.EnableElasticsearchRepositories;
@Configuration
@EnableElasticsearchRepositories(basePackages = "xx.xxx.domain.repository.elastic")
public class ElasticsearchConfiguration {
@Bean
public Client client() {
TransportClient client = new TransportClient();
client.addTransportAddress(new
InetSocketTransportAddress("127.0.0.1", 9300));
return client;
}
@Bean
public ElasticsearchOperations elasticsearchTemplate() {
return new ElasticsearchTemplate(client());
}
}
为什么执行elasticsearch的api会出错
5.3.3 条件运算符和条件表达式
如果在条件语句中，只执行单个的赋值语句时， 常可使用条件表达式来实现。不但使程序简洁，也提高了运行效率。
条件运算符为?和：，它是一个三目运算符，即有三个参与运算的量。
由条件运算符组成条件表达式的一般形式为：
表达式1? 表达式2： 表达式3
其求值规则为：如果表达式1的值为真，则以表达式2 的值作为条件表达式的值，否则以表达式2的值作为整个条件表达式的值。
条件表达式通常用于赋值语句之中。
例如条件语句：
if(a>b) max=a;
else max=b;
可用条件表达式写为
max=(a>b)?a:b;
扩展阅读：宫颈asc-us严重吗 ... asics kinsei blast ... elasticsearch api ... elasticsearch 简单入门 ... ascus是tct最轻的症状吗 ... elasticsearch官方文档 ... 宫颈asch是几级病变 ... elasticsearch面试题 ... we use plastic ...
