elastic/elasticsearch-servicewrapper

Consider Changing Default Start Order From S20 to at least S56

Opened this issue · 0 comments

When running ElasticSearch within Amazon EC2 and EBS backed volumes the default start order of S20 is too early and the EBS volumes are not actually mounted yet (S55ebs-mount).

Consider making the S20elasticsearch symlink S56elasticsearch to ensure that all EBS volumes have been correctly mounted prior to starting ElasticSearch.

If ElasticSearch starts prior to the EBS volumes being mounted ES detects that the mount point is / and the wrong device; instead of the proper mount point and device.