Ok. The shards are recovered now. I tried to set the ES_HEAP_SIZE to 2g, but I am still getting "Nodes not available" error:
<https://lh3.googleusercontent.com/-g8vS5TTJwP0/VAYM0Q0LbLI/AAAAAAAAAOU/zznAKLbY-z0/s1600/nonodes.jpg> What can be the cause then? Thanks! Yuheng On Tuesday, September 2, 2014 10:26:29 AM UTC-4, David Pilato wrote: > > You have to start again the second node on the same machine to get the > other shards back. Then when you cluster is yellow again, you can switch > off the second node. > > BTW, you should set ES_HEAP_SIZE instead of dealing with Xmx Xms (but this > will do the same thing behind the scene). See > http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html#_environment_variables > > -- > *David Pilato* | *Technical Advocate* | *Elasticsearch.com* > @dadoonet <https://twitter.com/dadoonet> | @elasticsearchfr > <https://twitter.com/elasticsearchfr> > > > Le 2 septembre 2014 à 16:14:31, Yuheng Du (yuheng....@gmail.com > <javascript:>) a écrit: > > I tired 2g, It only worked when I use ./elasticsearch -Xmx2g -Xms2g. > Currently some of my shards are stated as "unassigned" in my kopf web > interface. It happened after I started 3 nodes at the same time in my > desktop yesterday. > > There should be 3G of data in the cluster, but know I see only 1.92G. I > think some data is stored in another node in my machine but I don't know > how to fix it. > > > <https://lh3.googleusercontent.com/-RZb2tkusmlc/VAXQqoCriOI/AAAAAAAAAOE/omiptkABSuU/s1600/kopf.jpg> > How can I fix this issue? > > On Tuesday, September 2, 2014 10:04:40 AM UTC-4, David Pilato wrote: >> >> Try 2g >> >> >> -- >> David ;-) >> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs >> >> Le 2 sept. 2014 à 15:49, Yuheng Du <yuheng....@gmail.com> a écrit : >> >> I tried to run ./elasticsearch --node.name=esmaster -Xmx=2G -Xms=2G. >> But it gives me the error msg: Invalid maximum heap size: -Xmx=2G, >> >> How can I deal with this? >> >> Thanks >> >> On Tuesday, September 2, 2014 3:46:26 AM UTC-4, David Pilato wrote: >>> >>> Ha! On your desktop? So that's not a production issue. >>> >>> In that case, you should may be give more memory to all your >>> elasticsearch nodes. >>> What is your current HEAP size? >>> >>> -- >>> *David Pilato* | *Technical Advocate* | *Elasticsearch.com >>> <http://Elasticsearch.com>* >>> @dadoonet <https://twitter.com/dadoonet> | @elasticsearchfr >>> <https://twitter.com/elasticsearchfr> >>> >>> >>> Le 2 septembre 2014 à 09:17:31, Yuheng Du (yuheng....@gmail.com) a >>> écrit: >>> >>> Each query is doing a search in _all indexes in the cluster. Maybe >>> that's also a hold up of the availability of ES server. >>> >>> I tried to run 3 ES nodes on my desktop machine but it does not seems to >>> help, it also crashed after some time. >>> >>> On Tuesday, September 2, 2014 3:10:13 AM UTC-4, David Pilato wrote: >>>> >>>> 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 >>>> <http://Elasticsearch.com>* >>>> @dadoonet <https://twitter.com/dadoonet> | @elasticsearchfr >>>> <https://twitter.com/elasticsearchfr> >>>> >>>> >>>> Le 2 septembre 2014 à 08:53:13, Yuheng Du (yuheng....@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 elasticsearc...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/elasticsearch/6dace925-d2d8-443f-bc9d-1e333ef96890%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/elasticsearch/6dace925-d2d8-443f-bc9d-1e333ef96890%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 elasticsearc...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/elasticsearch/476fd9e6-71ee-4e14-9bd0-dd3cd1cc42ca%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/elasticsearch/476fd9e6-71ee-4e14-9bd0-dd3cd1cc42ca%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 elasticsearc...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/5fea40c8-7645-48e5-8d2a-02e18f5ef7cf%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/5fea40c8-7645-48e5-8d2a-02e18f5ef7cf%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 elasticsearc...@googlegroups.com <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/4b7432b3-3956-42c3-a258-ff596148157c%40googlegroups.com > > <https://groups.google.com/d/msgid/elasticsearch/4b7432b3-3956-42c3-a258-ff596148157c%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/ff5e5463-cf57-40b1-92ed-1405e3fb0402%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
