I have no idea. I don't know the Perl Client.
Does this works?
curl localhost:9200
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr
Le 2 septembre 2014 à 22:46:15, Yuheng Du (yuheng.du.hust@gmail.com) a écrit:
Tried to increase the memory for the VM, now ES runs ok, but still gives me error:
Which is caused by the Elasticsearch's perl module's Try::Tiny module.
How to remove this kind of warning/error?
Thanks.
On Tuesday, September 2, 2014 3:25:30 PM UTC-4, David Pilato wrote:
You don't have enough memory available on your laptop I guess...
--
David 
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 2 sept. 2014 à 21:05, Yuheng Du yuheng....@gmail.com a écrit :
Ok. you are right. I was able to set the maximum heap size and now it looks like:
"jvm" : {
"timestamp" : 1409684394790,
"uptime_in_millis" : 128401,
"mem" : {
"heap_used_in_bytes" : 520385872,
"heap_used_percent" : 24,
"heap_committed_in_bytes" : 2138767360,
"heap_max_in_bytes" : 2138767360,
"non_heap_used_in_bytes" : 46357584,
"non_heap_committed_in_bytes" : 46727168,
"pools" : {
"young" : {
"used_in_bytes" : 61936096,
"max_in_bytes" : 69795840,
"peak_used_in_bytes" : 69795840,
"peak_max_in_bytes" : 69795840
},
"survivor" : {
"used_in_bytes" : 8716288,
"max_in_bytes" : 8716288,
"peak_used_in_bytes" : 8716288,
"peak_max_in_bytes" : 8716288
},
"old" : {
"used_in_bytes" : 449733488,
"max_in_bytes" : 2060255232,
"peak_used_in_bytes" : 449733488,
"peak_max_in_bytes" : 2060255232
}
}
},
But when I start my two streaming data source which does the query, it simply get the ES instance killed. When I restart ES, I was told that:
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x000000077ad30000, 2060255232, 0) failed; error='Cannot allocate memory' (errno=12)
There is insufficient memory for the Java Runtime Environment to continue.
Native memory allocation (malloc) failed to allocate 2060255232 bytes for committing reserved memory.
An error report file with more information is saved as:
/home/yuheng/Downloads/elasticsearch-1.2.0/bin/hs_err_pid5116.log
Any thoughts?
On Tuesday, September 2, 2014 2:48:17 PM UTC-4, David Pilato wrote:
I think your JVM settings are incorrect as we can see with heap_max
--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 2 sept. 2014 à 20:37, Yuheng Du yuheng....@gmail.com a écrit :
BTW, the node stats info shows the jvm usage info as follows:
"jvm" : {
"timestamp" : 1409682903048,
"uptime_in_millis" : 488996,
"mem" : {
"heap_used_in_bytes" : 48476472,
"heap_used_percent" : 9,
"heap_committed_in_bytes" : 73412608,
"heap_max_in_bytes" : 515571712,
"non_heap_used_in_bytes" : 57043440,
"non_heap_committed_in_bytes" : 92200960,
"pools" : {
"young" : {
"used_in_bytes" : 12126760,
"max_in_bytes" : 69795840,
"peak_used_in_bytes" : 17367040,
"peak_max_in_bytes" : 69795840
},
"survivor" : {
"used_in_bytes" : 915456,
"max_in_bytes" : 8716288,
"peak_used_in_bytes" : 2097152,
"peak_max_in_bytes" : 8716288
},
"old" : {
"used_in_bytes" : 35434256,
"max_in_bytes" : 437059584,
"peak_used_in_bytes" : 38372208,
"peak_max_in_bytes" : 437059584
}
}
},
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 | @elasticsearchfr
Le 2 septembre 2014 à 16:14:31, Yuheng Du (yuheng....@gmail.com) 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.
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
@dadoonet | @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
@dadoonet | @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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/4891b5a1-5c3a-4d9e-85b7-5442707b9438%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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/etPan.54062daa.71f32454.d74c%40MacBook-Air-de-David.local.
For more options, visit https://groups.google.com/d/optout.
