Re: No node available exception
When i set the ping timeout for transport client to a higher value, the issue is fixed automatically. -- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/No-node-available-exception-tp4069387p4069408.html Sent from the ElasticSearch Users mailing list archive at Nabble.com. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1421897067953-4069408.post%40n3.nabble.com. For more options, visit https://groups.google.com/d/optout.
No node available exception
Hi, I am using transport client for ES. I have a search request for 1 million records. I am getting No node available exception after getting 8k records itself. What can be done to overcome this issue? Its very urgent please help. Thanks. -- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/No-node-available-exception-tp4069387.html Sent from the ElasticSearch Users mailing list archive at Nabble.com. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1421867488065-4069387.post%40n3.nabble.com. For more options, visit https://groups.google.com/d/optout.
Re: No node available Exception
We had the same problem. reason: The application server uses a older version of log4j than ES needed. Am Mittwoch, 4. Dezember 2013 19:31:26 UTC+1 schrieb Justin Uang: > > I get the same problem too. Our configuration has us using the > TransportClient, and we have a single node cluster using the loopback > interface. What's puzzling is that it only shows up intermittently. > > >>> -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/654f1d79-16d1-4cdf-9d06-db8a020affab%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
no node available exception after node shutdown
Hi folks,
we have a two node cluster and we connect to it using the TransportClient
from java by adding two hosts, i.e.
((TransportClient) client).addTransportAddress(new
InetSocketTransportAddress("elastic1", port));
((TransportClient) client).addTransportAddress(new
InetSocketTransportAddress("elastic2",
port));
The load-balancing *kind of *works, i.e. when I take down one host, the
cluster keeps working because we have index.number_of_replicas set to 1.
However, there is a little glitch (~2secs) just after a node shuts down. We
have lots of indexing/search requests going to the cluster all the time,
and when I shutdown one server, our system throws *No node available
*exceptions
(and recovers after ~2secs).
I thought that shutting down the node using the API by calling
curl -XPOST 'http://localhost:9200/_cluster/nodes/_local/_shutdown'
would fix this issue at least when I take the node down purposefully for
maintenance, but it's the same.
Is there any way to fix this, or do we just have to expect that sometimes
the cluster might not be available and retry?
Thanks,
emanuel
--
Emanuel Buzek
Software Engineer, ROKE.cz
tel: +420 776 54 26 26
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAL1sZ7%3DmdN35Ex%2Bckc_LEhUPLjOVaUS8eB2kP4us-tsBFWxhtA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
getting no node available exception when there are many requests
Hello all,
I'm using storm with elasticsearch percolator and normally it works as
expected.
but when there are to many requests simultaneously, some of them succeed
and some fail with no node available exception.
I think there should be a configuration about maximum requests per seconds
or something like that, and should be a way to avoid no node available
exception by queing request in the java ElasticSearch client.
Below is my code snippet for percolating
client.preparePercolate()
.setIndices("index")
.setDocumentType(projectName)
.setPercolateDoc(docBuilder().setDoc(log)).execute().actionGet();
would be glad to let me know if you have any knowledge about this, thanks.
Sincerly,
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAL3_U408zgZmwLdu-SkEs%3DaZ_GFszAk1GKk6vuHbTSjutP2%3D4g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: TransportClient of ES 1.1.1 on Ubantu 12.x throws 'No node available' exception
But be aware that there is a bug in Elasticsearch which can cause the transport client to get the NoNodeAvailable exception of sniff is set to false. It doesn't seem to have been the issue in this case but I thought I should mention it. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/70b8dab6-4032-4016-adb6-427781dc7531%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: TransportClient of ES 1.1.1 on Ubantu 12.x throws 'No node available' exception
Thanks David, .bashrc had PATH set for 2 versions. One was overriding the
other
On Wednesday, May 28, 2014 3:02:29 PM UTC+5:30, David Pilato wrote:
> It sounds like you are mixing elasticsearch versions (client and node) or
> JVM versions.
>
> --
> David ;-)
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
>
>
> Le 28 mai 2014 à 10:34, Chetana > a
> écrit :
>
> ES log shows this warning message, 'transport.netty- Message not fully
> read (request) for [0] and action [], resetting'
> On Wednesday, May 28, 2014 12:07:39 PM UTC+5:30, Chetana wrote:
>
>> I have ugraded ES from 0.90.2 to ES 1.1.1 recently. I am able to get the
>> Tranpsort client of ES 1.1.1 and create mapping on Windows 2010. But I get
>> a 'No node available' exception on Ubantu 12.x
>>
>> Here is the code I use for connecting to ES
>>
>> ImmutableSettings.Builder settingsBuilder =
>> ImmutableSettings.settingsBuilder();
>>
>> // because default cluster name used
>> //settingsBuilder.put("cluster.name", "elasticsearch");
>>
>> TransportClient client = new TransportClient(settingsBuilder.build());
>> client.addTransportAddress(new InetSocketTransportAddress(
>> "localhost",
>> 9300));
>>
>>client.admin().cluster().prepareHealth()
>> .setWaitForYellowStatus()
>> .setTimeout(TimeValue.timeValueMinutes(1)) .execute() .actionGet();
>>
>> CreateIndexRequestBuilder builder =
>> client.admin().indices().prepareCreate("sample").setSettings(settings);
>> client.admin().indices().create(builder.request()).get();
>> PutMappingRequestBuilder putBuilder =
>> client.admin().indices().preparePutMapping("sample");
>> putBuilder.setType("sample");
>>
>> XContentBuilder parentMapping
>> =
>> XContentFactory.jsonBuilder().startObject().startObject("sample").field("include_in_all",false).endObject().endObject();
>>
>> putBuilder.setSource(parentMapping);
>> client.admin().indices().putMapping(putBuilder.request()).get();
>>
>> Am I missing any setting? Please suggest how to trobleshoot this issue
>>
>> Thanks
>>
> --
> 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 elasticsearc...@googlegroups.com .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/228ae7a0-d688-443f-88c2-127b708810dd%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/228ae7a0-d688-443f-88c2-127b708810dd%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/c0d0a81e-cec0-46c4-9e3d-85410207dbd5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: TransportClient of ES 1.1.1 on Ubantu 12.x throws 'No node available' exception
It sounds like you are mixing elasticsearch versions (client and node) or JVM
versions.
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 28 mai 2014 à 10:34, Chetana a écrit :
ES log shows this warning message, 'transport.netty- Message not fully read
(request) for [0] and action [], resetting'
> On Wednesday, May 28, 2014 12:07:39 PM UTC+5:30, Chetana wrote:
> I have ugraded ES from 0.90.2 to ES 1.1.1 recently. I am able to get the
> Tranpsort client of ES 1.1.1 and create mapping on Windows 2010. But I get a
> 'No node available' exception on Ubantu 12.x
>
> Here is the code I use for connecting to ES
>
> ImmutableSettings.Builder settingsBuilder =
> ImmutableSettings.settingsBuilder();
>
> // because default cluster name used
> //settingsBuilder.put("cluster.name", "elasticsearch");
>
> TransportClient client = new TransportClient(settingsBuilder.build());
> client.addTransportAddress(new InetSocketTransportAddress(
> "localhost",
> 9300));
>
>client.admin().cluster().prepareHealth()
> .setWaitForYellowStatus() .setTimeout(TimeValue.timeValueMinutes(1))
> .execute() .actionGet();
>
> CreateIndexRequestBuilder builder =
> client.admin().indices().prepareCreate("sample").setSettings(settings);
> client.admin().indices().create(builder.request()).get();
> PutMappingRequestBuilder putBuilder =
> client.admin().indices().preparePutMapping("sample");
> putBuilder.setType("sample");
>
> XContentBuilder parentMapping =
> XContentFactory.jsonBuilder().startObject().startObject("sample").field("include_in_all",false).endObject().endObject();
>
> putBuilder.setSource(parentMapping);
> client.admin().indices().putMapping(putBuilder.request()).get();
>
> Am I missing any setting? Please suggest how to trobleshoot this issue
>
> Thanks
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/228ae7a0-d688-443f-88c2-127b708810dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/FA4BBE61-B6B5-442A-9D60-1A7FC1DAB80C%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.
Re: TransportClient of ES 1.1.1 on Ubantu 12.x throws 'No node available' exception
ES log shows this warning message, 'transport.netty- Message not fully read
(request) for [0] and action [], resetting'
On Wednesday, May 28, 2014 12:07:39 PM UTC+5:30, Chetana wrote:
> I have ugraded ES from 0.90.2 to ES 1.1.1 recently. I am able to get the
> Tranpsort client of ES 1.1.1 and create mapping on Windows 2010. But I get
> a 'No node available' exception on Ubantu 12.x
>
> Here is the code I use for connecting to ES
>
> ImmutableSettings.Builder settingsBuilder =
> ImmutableSettings.settingsBuilder();
>
> // because default cluster name used
> //settingsBuilder.put("cluster.name", "elasticsearch");
>
> TransportClient client = new TransportClient(settingsBuilder.build());
> client.addTransportAddress(new InetSocketTransportAddress(
> "localhost",
> 9300));
>
>client.admin().cluster().prepareHealth()
> .setWaitForYellowStatus()
> .setTimeout(TimeValue.timeValueMinutes(1)) .execute() .actionGet();
>
> CreateIndexRequestBuilder builder =
> client.admin().indices().prepareCreate("sample").setSettings(settings);
> client.admin().indices().create(builder.request()).get();
> PutMappingRequestBuilder putBuilder =
> client.admin().indices().preparePutMapping("sample");
> putBuilder.setType("sample");
>
> XContentBuilder parentMapping
> =
> XContentFactory.jsonBuilder().startObject().startObject("sample").field("include_in_all",false).endObject().endObject();
>
> putBuilder.setSource(parentMapping);
> client.admin().indices().putMapping(putBuilder.request()).get();
>
> Am I missing any setting? Please suggest how to trobleshoot this issue
>
> Thanks
>
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/228ae7a0-d688-443f-88c2-127b708810dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
TransportClient of ES 1.1.1 on Ubantu 12.x throws 'No node available' exception
I have ugraded ES from 0.90.2 to ES 1.1.1 recently. I am able to get the
Tranpsort client of ES 1.1.1 and create mapping on Windows 2010. But I get
a 'No node available' exception on Ubantu 12.x
Here is the code I use for connecting to ES
ImmutableSettings.Builder settingsBuilder =
ImmutableSettings.settingsBuilder();
// because default cluster name used
//settingsBuilder.put("cluster.name", "elasticsearch");
TransportClient client = new TransportClient(settingsBuilder.build());
client.addTransportAddress(new InetSocketTransportAddress(
"localhost",
9300));
client.admin().cluster().prepareHealth()
.setWaitForYellowStatus()
.setTimeout(TimeValue.timeValueMinutes(1)) .execute() .actionGet();
CreateIndexRequestBuilder builder =
client.admin().indices().prepareCreate("sample").setSettings(settings);
client.admin().indices().create(builder.request()).get();
PutMappingRequestBuilder putBuilder =
client.admin().indices().preparePutMapping("sample");
putBuilder.setType("sample");
XContentBuilder parentMapping
=
XContentFactory.jsonBuilder().startObject().startObject("sample").field("include_in_all",false).endObject().endObject();
putBuilder.setSource(parentMapping);
client.admin().indices().putMapping(putBuilder.request()).get();
Am I missing any setting? Please suggest how to trobleshoot this issue
Thanks
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/0755547c-ca4e-43dd-a09b-c778a4bb4687%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Getting 'No Node Available Exception' while using TrasnsportClient of ElasticSearch.
Hi, I am pretty new to Elastic Search. I have following things in my code OR looking for solution to 'No Node Available Exception' problem in the following scenario. 1) We have ES running on System with 1 Node and 1 Cluster 2) We have 4 indexes on ES. (Each index has different type of data, Example: Customer Preference / Customer Address / Customer Interests / Customer Basic Details) 3) We have WebApplication (as webservice) running on Tomcat. 4) We are calling webservice method as Controller's. -This will receive request from consumers in the form JSON data. 5) Based on that data(Example: If consumers asks for Customer Preference for given customer Id then we go to 'Customer Preferences' index) we will go to service(using Spring) layers. 6) In each of the service layer we get TransportClient instance in SingleTon object and wait for its response and return the result to Controller. In a Scenario if consumer asks for all 4 types of data for a Customer, and if we ask first for preference, address, interests and basic details in sequence. It works well. But this adds to performance. So we want these things to process and get data parallel. So we used Spring Task Executors to do this parallel. In that case we get data from one index and others will get 'No Node Available Exception'. Its pretty random to on say on which data we get this problem. Pleas help me here. Thanks in advance! -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/3ea880bf-c0f0-44bf-81e8-8b9f5529483c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
No Node available exception while connection to elasticsearch cluster
Hi,
I am using a three node cluster with two ip address on each server. I want
http and transport addresses to be separated to avoid network congestion.
*http.host:* 192.168.1.113 (binded on eth0)
*transport.host:* 192.168.10.116 (binded on eth1)
and similar for all other nodes.
The nodes are connecting to each other perfectly, and i can create index,
and ad data to it by using curl command.
But when create connection through java program the i get a no node
available exception.
I am using following code for creating connection.
Settings s = ImmutableSettings.settingsBuilder().put("cluster.name",
"orkashcluster_es").build();
TransportClient tmp = new TransportClient(s);
tmp.addTransportAddress(new
InetSocketTransportAddress("192.168.10.116", 9300)); // have also tried
with 192.168.1.116
client = tmp;
Please let me know what i am doing wrong.
Regards,
Bharvi Dixit
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/ef0970a3-a9b1-4cfd-9895-9dbe05262b13%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
