Upstart / Systemd services #424
Milestone
Comments
|
@runningman84 I'd welcome a PR to that effect, and be glad to review it. Ideally, this kind of work would get incorporated upstream in the ES packaging for RPM/DEB, and then we'd include it here, too. |
Closed
martinb3
added a commit
that referenced
this issue
Oct 28, 2016
- Drop support for ES < 5.0 * Remove the shield/watcher plugin installs, since they have become x-pack in ES 5.0 * Remove hashes and different download URLs, other logic that distinguishes between 1.x and 2.x. * Update README.md to reflect that this change drops support for < 5.0 (too many changes) - elasticsearch_install: * Drop warnings for installing as root under ES < 2.0 - elasticsearch_configure: * Replace logging.yml with new log4j2.properties file, add template for this * Update variables that are allowed in /etc/sysconfig/elasticsearch or /etc/default/elasticsearch * Drop ES_JAVA_OPTS and introduce option 'jvm_options' with new template for /etc/elasticsearch/jvm.options * Add new restart_on_upgrade option, drop thread_stack_size, drop env_options, drop gc_settings * Drop some of the defaults in elasticsearch.yml that are no longer present in upstream packaging - elasticsearch_plugin: * change bin/plugin to bin/elasticsearch-plugin when managing plugins * Remove the shield/watcher plugin installs, since they have become x-pack in ES 5.0 * Add new `options` parameter/attribute so that you can pass things like `--batch` to this resource - elasticsearch_service: * Introduce systemd unit files for distros that support them * Guard on which init systems based on presence of /etc/init.d or /usr/lib/systemd/system directories Fixes #424. Fixes #478. Fixes #503.
martinb3
added a commit
that referenced
this issue
Oct 28, 2016
- Drop support for ES < 5.0 * Remove the shield/watcher plugin installs, since they have become x-pack in ES 5.0 * Remove hashes and different download URLs, other logic that distinguishes between 1.x and 2.x. * Update README.md to reflect that this change drops support for < 5.0 (too many changes) - elasticsearch_install: * Drop warnings for installing as root under ES < 2.0 - elasticsearch_configure: * Replace logging.yml with new log4j2.properties file, add template for this * Update variables that are allowed in /etc/sysconfig/elasticsearch or /etc/default/elasticsearch * Drop ES_JAVA_OPTS and introduce option 'jvm_options' with new template for /etc/elasticsearch/jvm.options * Add new restart_on_upgrade option, drop thread_stack_size, drop env_options, drop gc_settings * Drop some of the defaults in elasticsearch.yml that are no longer present in upstream packaging - elasticsearch_plugin: * change bin/plugin to bin/elasticsearch-plugin when managing plugins * Remove the shield/watcher plugin installs, since they have become x-pack in ES 5.0 * Add new `options` parameter/attribute so that you can pass things like `--batch` to this resource - elasticsearch_service: * Introduce systemd unit files for distros that support them, copy latest init scripts for all platforms * Guard on which init systems based on presence of /etc/init.d or /usr/lib/systemd/system directories Fixes #424. Fixes #478. Fixes #503.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be great if the cookbook would also support upstart and systemd services which would allow an auto-recovery of crashed elasticsearch instances?
The text was updated successfully, but these errors were encountered: