By the looks of things, you should look for a new provider as they are
doing some things on the underlying hypervisor restricting ES from locking
memory access.

However your heap size is very small, how much data is in your cluster.

On 20 March 2015 at 07:13, Yashin Soraballee <yashin.sorabal...@gmail.com>
wrote:

> Hello guys,
> I am trying to run elasticsearch on a VPS server running CentOS with 4GB
> of RAM. It starts successfully but with the following errors and warning
> message below.
>
>
> # sudo service elasticsearch start
> error: permission denied on key 'vm.max_map_count'
> Starting elasticsearch: [ OK ]
> root@vps15042 [~]# log4j:WARN No appenders could be found for logger
> (common)
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
> morefo.
>
>
> As you can notice, there is no permission to set the vm.max_map_count
> setting on this VPS server ( even with root access ). So the only way to
> get rid of the message is by commenting the max_map_count setting out.
>
>  It then runs for a maximum of 4 hours and then tell me "Elastic service
> dead but pid still exists". It is most probably running out of memory and
> getting killed. The following is a log report as such :
>
>
> Mar 18 22:37:51 ecvp156s kernel: [3712702.735583] 22234 (java) invoked
> oom-killer in ub 15042 generation 0 gfp 0x200d2
> Mar 18 22:37:51 ecvp156s kernel: [3712702.736531] UB-15042-Mem-Info:
> Mar 18 22:37:51 ecvp156s kernel: [3712702.756570] Out of memory in UB
> 15042: OOM killed process 22232 (java) score 0 vm:7815680kB, rss:3786544kB,
> swap:0kB
> Mar 18 22:37:52 ecvp156s kernel: [3712703.677851] oom-killer in ub 15042
> generation 0 ends: task died
> Mar 18 22:38:21 ecvp156s kernel: [3712732.546844] 25904 (java) invoked
> oom-killer in ub 15042 generation 1 gfp 0x200d2
> Mar 18 22:38:21 ecvp156s kernel: [3712732.547766] UB-15042-Mem-Info:
> Mar 18 22:38:21 ecvp156s kernel: [3712732.567524] Out of memory in UB
> 15042: OOM killed process 25901 (java) score 0 vm:7815680kB, rss:3781624kB,
> swap:0kB
> Mar 18 22:38:22 ecvp156s kernel: [3712733.475601] oom-killer in ub 15042
> generation 1 ends: task died
> Mar 19 00:24:42 ecvp156s kernel: [3719119.150426] UB-9340-Mem-Info:
>
>
> My host provider is telling me to increase the amount of RAM. However I am
> running ES on a windows surface pro tablet with 4GB of RAM and core i3, and
> I am getting absolutely no issues with not a so powerful machine. Can I
> change some configurations to make it work perfectly? I've already tried
> the following and other combinations, but nothing keeps it running for long
> :
>
> /etc/security/limits.conf
> elasticsearch hard memlock 300000
>
> /etc/sysconfig/elasticsearch
> ES_HEAP_SIZE 1g
> MAX_LOCKED_MEMORY to 300000
>
> /etc/elasticsearch/elasticsearch.yml
> index.number_of_shards: 1
> index.number_of_replicas: 0
> index.term_index_interval: 256
> index.term_index_divisor: 5
>
> bootstrap.mlockall: true
>
> Thank you for your time. I am stuck with this and I'll have to change
> server if I cannot resolve 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/73d39af1-9254-4bce-9590-789554db90fb%40googlegroups.com
> <https://groups.google.com/d/msgid/elasticsearch/73d39af1-9254-4bce-9590-789554db90fb%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/CAEYi1X_LUZ5bN9XMyMxh4KseQJ%3D%3DmYxYSb_jiPT-vyuu-2o6_g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to