Java Indexing API : error in existing instance, ok with fresh one

Hi

We are implementing an indexer using JAVA API. When we launch the indexer
on a fresh 0.90.1 instance with no data, it just works fine, but when it is
launched on an existing ES instance, we get a "NoNodeAvailable" exception.
The instance is up with a yellow status.

org.elasticsearch.client.transport.NoNodeAvailableException: No node available
at org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:202)
at org.elasticsearch.client.transport.support.InternalTransportIndicesAdminClient.execute(InternalTransportIndicesAdminClient.java:85)
at org.elasticsearch.client.support.AbstractIndicesAdminClient.exists(AbstractIndicesAdminClient.java:147)
at org.elasticsearch.action.admin.indices.exists.indices.IndicesExistsRequestBuilder.doExecute(IndicesExistsRequestBuilder.java:43)
at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:62)
at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:57)

Any idea to investigate ?

Thanks.

Regards,

Yann

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

You are using IndicesExistsRequestBuilder.Maybe you are looking for an
index or index alias that does not exist.

Jörg

On Monday, June 3, 2013 11:13:00 AM UTC+2, Yann Barraud wrote:

Hi

We are implementing an indexer using JAVA API. When we launch the indexer
on a fresh 0.90.1 instance with no data, it just works fine, but when it is
launched on an existing ES instance, we get a "NoNodeAvailable" exception.
The instance is up with a yellow status.

org.elasticsearch.client.transport.NoNodeAvailableException: No node available
at org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:202)
at org.elasticsearch.client.transport.support.InternalTransportIndicesAdminClient.execute(InternalTransportIndicesAdminClient.java:85)
at org.elasticsearch.client.support.AbstractIndicesAdminClient.exists(AbstractIndicesAdminClient.java:147)
at org.elasticsearch.action.admin.indices.exists.indices.IndicesExistsRequestBuilder.doExecute(IndicesExistsRequestBuilder.java:43)
at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:62)
at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:57)

Any idea to investigate ?

Thanks.

Regards,

Yann

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hi,

We first check if the index exists using
client.admin().indices().prepareExists(indexName).execute().actionGet().isExists()
Then we are attempting creating the index using
client.admin().indices().prepareCreate(indexName).execute().actionGet().isAcknowledged()

Is it wrong ?

Le lundi 3 juin 2013 11:20:19 UTC+2, Jörg Prante a écrit :

You are using IndicesExistsRequestBuilder.Maybe you are looking for an

index or index alias that does not exist.

Jörg

On Monday, June 3, 2013 11:13:00 AM UTC+2, Yann Barraud wrote:

Hi

We are implementing an indexer using JAVA API. When we launch the indexer
on a fresh 0.90.1 instance with no data, it just works fine, but when it is
launched on an existing ES instance, we get a "NoNodeAvailable" exception.
The instance is up with a yellow status.

org.elasticsearch.client.transport.NoNodeAvailableException: No node available
at org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:202)
at org.elasticsearch.client.transport.support.InternalTransportIndicesAdminClient.execute(InternalTransportIndicesAdminClient.java:85)
at org.elasticsearch.client.support.AbstractIndicesAdminClient.exists(AbstractIndicesAdminClient.java:147)
at org.elasticsearch.action.admin.indices.exists.indices.IndicesExistsRequestBuilder.doExecute(IndicesExistsRequestBuilder.java:43)
at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:62)
at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:57)

Any idea to investigate ?

Thanks.

Regards,

Yann

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

OK, Thanks David Pilato : we were using specific clusternames.

http://www.elasticsearch.org/guide/reference/java-api/client/#transportclient
Have to set this in client config file.

Le lundi 3 juin 2013 11:41:04 UTC+2, Yann Barraud a écrit :

Hi,

We first check if the index exists using

client.admin().indices().prepareExists(indexName).execute().actionGet().isExists()
Then we are attempting creating the index using

client.admin().indices().prepareCreate(indexName).execute().actionGet().isAcknowledged()

Is it wrong ?

Le lundi 3 juin 2013 11:20:19 UTC+2, Jörg Prante a écrit :

You are using IndicesExistsRequestBuilder.Maybe you are looking for an

index or index alias that does not exist.

Jörg

On Monday, June 3, 2013 11:13:00 AM UTC+2, Yann Barraud wrote:

Hi

We are implementing an indexer using JAVA API. When we launch the
indexer on a fresh 0.90.1 instance with no data, it just works fine, but
when it is launched on an existing ES instance, we get a "NoNodeAvailable"
exception.
The instance is up with a yellow status.

org.elasticsearch.client.transport.NoNodeAvailableException: No node available
at org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:202)
at org.elasticsearch.client.transport.support.InternalTransportIndicesAdminClient.execute(InternalTransportIndicesAdminClient.java:85)
at org.elasticsearch.client.support.AbstractIndicesAdminClient.exists(AbstractIndicesAdminClient.java:147)
at org.elasticsearch.action.admin.indices.exists.indices.IndicesExistsRequestBuilder.doExecute(IndicesExistsRequestBuilder.java:43)
at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:62)
at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:57)

Any idea to investigate ?

Thanks.

Regards,

Yann

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.