Best practise is to use half of system ram for your heap, so ideally you should be setting it to 256mb. However you probably want to add more system RAM as you're hitting the limits with what you have.
Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [email protected] web: www.campaignmonitor.com On 24 February 2014 09:48, Mehdi <[email protected]> wrote: > Yes, Elasticsearch was deployed on the Vps 3 months ago, it worked > perfectly, until today. > > VPS config : *512MB Ram, 20GB SSD Disk* > > Le dimanche 23 février 2014 22:45:05 UTC, David Pilato a écrit : >> >> Do you have already some indexed data? >> If so, may be 512m is not enough. It's a really low value. >> >> -- >> David ;-) >> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs >> >> Le 23 févr. 2014 à 23:30, Mehdi <[email protected]> a écrit : >> >> Same result, i tried also this command: *rcelasticsearch console* >> >> wrapper | Launching a JVM... >> wrapper | JVM exited while loading the application. >> jvm 1 | Error occurred during initialization of VM >> jvm 1 | Could not reserve enough space for object heap >> wrapper | Encountered an invalid numerical value for configuration >> property wrapper.java.initmemory=512m. Resolving to 512. >> >> >> >> Le dimanche 23 février 2014 21:48:23 UTC, David Pilato a écrit : >>> >>> What happen if you try 512m instead of 512 >>> >>> >>> -- >>> David ;-) >>> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs >>> >>> >>> Le 23 févr. 2014 à 21:29, Mehdi <[email protected]> a écrit : >>> >>> Hi guys, >>> >>> It seems that Elasticsearch stops working this morning. >>> When i launch : sudo service elasticsearch start, it says : *Starting >>> ElasticSearch Server Done* >>> >>> But when i check the status, it gives me : *elasticsearch is not >>> running* >>> >>> I tried to launch it by the command : >>> /usr/share/elasticsearch/bin/elasticsearch >>> start >>> it gives me : >>> >>> >>> *Error occurred during initialization of VM Could not reserve enough >>> space for object heap* >>> >>> I tried to set 512m for Heap size in : /usr/share/elasticsearch/bin/ >>> service/elasticsearch.conf >>> >>> set.default.ES_HOME=<Path to ElasticSearch Home> >>> set.default.ES_HEAP_SIZE=512 >>> >>> >>> >>> But it didn't work. >>> How could i fix that? >>> >>> -- >>> 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 [email protected]. >>> To view this discussion on the web visit https://groups.google.com/d/ >>> msgid/elasticsearch/60c061b5-ad47-4067-8128-0df0a0098844% >>> 40googlegroups.com. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> -- >> 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 [email protected]. >> To view this discussion on the web visit https://groups.google.com/d/ >> msgid/elasticsearch/4c939f90-02ba-4d5c-8ced-1161c666346a% >> 40googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/65a4762f-8da3-45a5-b3ae-c59d2f01dc2d%40googlegroups.com > . > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEM624YGs0qirg70xwahY9yPZ0hez4h%2Bz4H4hdpmFb8T09wYoA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
