amazon ec2 - Elasticsearch fails to start -
i'm trying implement 2 node es cluster using amazon ec2 instances. after setup , try start es, fails start. below config files:
/etc/elasticsearch/elasticsearch.yml - http://pastebin.com/3q1qnqmz
/etc/init.d/elasticsearch - http://pastebin.com/f3ajyurr
below /var/log/elasticsearch/es-cluster.log content -
[2014-06-08 07:06:01,761][warn ][common.jna ] unknown mlockall error 0 [2014-06-08 07:06:02,095][info ][node ] [logstash] version[0.90.13], pid[29666], build[249c9c5/2014-03-25t15:27:12z] [2014-06-08 07:06:02,095][info ][node ] [logstash] initializing ... [2014-06-08 07:06:02,108][info ][plugins ] [logstash] loaded [], sites [] [2014-06-08 07:06:07,504][info ][node ] [logstash] initialized [2014-06-08 07:06:07,510][info ][node ] [logstash] starting ... [2014-06-08 07:06:07,646][info ][transport ] [logstash] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/10.164.27.207:9300]} [2014-06-08 07:06:12,177][info ][cluster.service ] [logstash] new_master [logstash][vcs_3lzeseksn-thhgwega][inet[/<an_ip_is_here>:9300]], reason: zen-disco-join (elected_as_master) [2014-06-08 07:06:12,208][info ][discovery ] [logstash] es-cluster/vcs_3lzeseksn-thhgwega [2014-06-08 07:06:12,334][info ][http ] [logstash] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/<an_ip_is_here>:9200]} [2014-06-08 07:06:12,335][info ][node ] [logstash] started [2014-06-08 07:06:12,379][info ][gateway ] [logstash] recovered [0] indices cluster_state
i see several things should correct in configuration files.
1) need different node names. using same config file both nodes. not want if setting node name are: node.name: "logstash"
. either create separate configuration files different node.name entries or comment out , let es auto assign node.name.
2) mlockall setting throwing error. not start out setting bootstrap.mlockall: true
until you've first gotten es run without , have spent little time configuring linux support it. can cause problems booting up:
warning
mlockall might cause jvm or shell session exit if tries allocate more memory available!
i'd check out documentation on configuration variables , careful making many adjustments right out of gate.
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-service.html
if want make memory adjustments es previous stackoverflow article should helpful:
Comments
Post a Comment