It seems that the TransportClient is broken on master:
Code:
client = new TransportClient(settings).addTransportAddress(new
InetSocketTransportAddress("localhost", 9300));
client.admin().indices().prepareCreate(indexName)....execute().actionGet();
Result:
Exception in thread "main"
org.elasticsearch.client.transport.NoNodeAvailableException: No node
available
at org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:170)
at org.elasticsearch.client.transport.support.InternalTransportIndicesAdminClient.create(InternalTransportIndicesAdminClient.java:252)
at org.elasticsearch.client.action.admin.indices.create.CreateIndexRequestBuilder.doExecute(CreateIndexRequestBuilder.java:158)
at org.elasticsearch.client.action.admin.indices.support.BaseIndicesRequestBuilder.execute(BaseIndicesRequestBuilder.java:52)
at org.elasticsearch.client.action.admin.indices.support.BaseIndicesRequestBuilder.execute(BaseIndicesRequestBuilder.java:47)
It seems that the TransportClient is broken on master:
Code:
client = new TransportClient(settings).addTransportAddress(new
InetSocketTransportAddress("localhost", 9300));
client.admin().indices().prepareCreate(indexName)....execute().actionGet();
Result:
Exception in thread "main"
org.elasticsearch.client.transport.NoNodeAvailableException: No node
available
at
org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:170)
at
org.elasticsearch.client.transport.support.InternalTransportIndicesAdminClient.create(InternalTransportIndicesAdminClient.java:252)
at
org.elasticsearch.client.action.admin.indices.create.CreateIndexRequestBuilder.doExecute(CreateIndexRequestBuilder.java:158)
at
org.elasticsearch.client.action.admin.indices.support.BaseIndicesRequestBuilder.execute(BaseIndicesRequestBuilder.java:52)
at
org.elasticsearch.client.action.admin.indices.support.BaseIndicesRequestBuilder.execute(BaseIndicesRequestBuilder.java:47)
It seems that the TransportClient is broken on master:
Code:
client = new TransportClient(settings).addTransportAddress(new
InetSocketTransportAddress("localhost", 9300));
client.admin().indices().prepareCreate(indexName)....execute().actionGet();
Result:
Exception in thread "main"
org.elasticsearch.client.transport.NoNodeAvailableException: No node
available
at
org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:170)
at
org.elasticsearch.client.transport.support.InternalTransportIndicesAdminClient.create(InternalTransportIndicesAdminClient.java:252)
at
org.elasticsearch.client.action.admin.indices.create.CreateIndexRequestBuilder.doExecute(CreateIndexRequestBuilder.java:158)
at
org.elasticsearch.client.action.admin.indices.support.BaseIndicesRequestBuilder.execute(BaseIndicesRequestBuilder.java:52)
at
org.elasticsearch.client.action.admin.indices.support.BaseIndicesRequestBuilder.execute(BaseIndicesRequestBuilder.java:47)
Ok my bad, it works. The problem was actually that I tried to start
master using the same command line / data directory than for my 0.17.7
instance, and elasticsearch failed to start (failed to acquire lock),
so I started it just with ./elasticsearch -f and the default
clustername. Long story short: the TransportClient works, but master
doesn't want to start with my current command line:
It seems that the TransportClient is broken on master:
Code:
client = new TransportClient(settings).addTransportAddress(new
InetSocketTransportAddress("localhost", 9300));
client.admin().indices().prepareCreate(indexName)....execute().actionGet();
Result:
Exception in thread "main"
org.elasticsearch.client.transport.NoNodeAvailableException: No node
available
at
org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:170)
at
org.elasticsearch.client.transport.support.InternalTransportIndicesAdminClient.create(InternalTransportIndicesAdminClient.java:252)
at
org.elasticsearch.client.action.admin.indices.create.CreateIndexRequestBuilder.doExecute(CreateIndexRequestBuilder.java:158)
at
org.elasticsearch.client.action.admin.indices.support.BaseIndicesRequestBuilder.execute(BaseIndicesRequestBuilder.java:52)
at
org.elasticsearch.client.action.admin.indices.support.BaseIndicesRequestBuilder.execute(BaseIndicesRequestBuilder.java:47)
Ok my bad, it works. The problem was actually that I tried to start
master using the same command line / data directory than for my 0.17.7
instance, and elasticsearch failed to start (failed to acquire lock),
so I started it just with ./elasticsearch -f and the default
clustername. Long story short: the TransportClient works, but master
doesn't want to start with my current command line:
Ok my bad, it works. The problem was actually that I tried to start
master using the same command line / data directory than for my 0.17.7
instance, and elasticsearch failed to start (failed to acquire lock),
so I started it just with ./elasticsearch -f and the default
clustername. Long story short: the TransportClient works, but master
doesn't want to start with my current command line:
It seems that the TransportClient is broken on master:
Code:
client = new TransportClient(settings).addTransportAddress(new
InetSocketTransportAddress("localhost", 9300));
client.admin().indices().prepareCreate(indexName)....execute().actionGet();
Result:
Exception in thread "main"
org.elasticsearch.client.transport.NoNodeAvailableException: No node
available
at
org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:170)
at
org.elasticsearch.client.transport.support.InternalTransportIndicesAdminClient.create(InternalTransportIndicesAdminClient.java:252)
at
org.elasticsearch.client.action.admin.indices.create.CreateIndexRequestBuilder.doExecute(CreateIndexRequestBuilder.java:158)
at
org.elasticsearch.client.action.admin.indices.support.BaseIndicesRequestBuilder.execute(BaseIndicesRequestBuilder.java:52)
at
Ok my bad, it works. The problem was actually that I tried to start
master using the same command line / data directory than for my 0.17.7
instance, and elasticsearch failed to start (failed to acquire lock),
so I started it just with ./elasticsearch -f and the default
clustername. Long story short: the TransportClient works, but master
doesn't want to start with my current command line:
Ok my bad, it works. The problem was actually that I tried to start
master using the same command line / data directory than for my 0.17.7
instance, and elasticsearch failed to start (failed to acquire lock),
so I started it just with ./elasticsearch -f and the default
clustername. Long story short: the TransportClient works, but master
doesn't want to start with my current command line:
It seems that the TransportClient is broken on master:
Code:
client = new TransportClient(settings).addTransportAddress(new
InetSocketTransportAddress("localhost", 9300));
client.admin().indices().prepareCreate(indexName)....execute().actionGet();
Result:
Exception in thread "main"
org.elasticsearch.client.transport.NoNodeAvailableException: No
node
available
at
org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:170)
at
org.elasticsearch.client.transport.support.InternalTransportIndicesAdminClient.create(InternalTransportIndicesAdminClient.java:252)
at
org.elasticsearch.client.action.admin.indices.create.CreateIndexRequestBuilder.doExecute(CreateIndexRequestBuilder.java:158)
at
org.elasticsearch.client.action.admin.indices.support.BaseIndicesRequestBuilder.execute(BaseIndicesRequestBuilder.java:52)
at
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.