Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider Changing Default Start Order From S20 to at least S56 #29

Open
cadams500 opened this issue Jul 26, 2013 · 0 comments
Open

Consider Changing Default Start Order From S20 to at least S56 #29

cadams500 opened this issue Jul 26, 2013 · 0 comments

Comments

@cadams500
Copy link

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.

@ghost ghost assigned dadoonet Jul 29, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants