May be you could increase the number of replicas and nodes so your cluster could handle more queries at a time. The main cost is of course in term of machine and disk space.
Can't tell really more without more details about what you are doing exactly. May be others have some ideas? -- David Pilato | Technical Advocate | Elasticsearch.com @dadoonet | @elasticsearchfr Le 2 septembre 2014 à 08:53:13, Yuheng Du (yuheng.du.h...@gmail.com) a écrit: Hi guys, I have some streaming sensor data as input to ES. For each incoming data message, I need to do a query on the historic data in ES according to the 'timestamp' and 'messageId' in that message. I need to get the aggregated query results in real-time. My problem is each data message may sprout 28 queries at approximately the same time and I get [No-nodes available] error from ES frequently. Can anyone suggest what is the cause of this error and how can I fix it? Or should I use some other system to handle this problem like apache storm? Thanks! Yuheng -- 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/6dace925-d2d8-443f-bc9d-1e333ef96890%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/etPan.54056d43.741226bb.6ef9%40MacBook-Air-de-David.local. For more options, visit https://groups.google.com/d/optout.
