elasticsearch: RESTART_ON_UPGRADE is configurable
This commit is contained in:
parent
9bf70a57f4
commit
62a85ef72a
|
@ -15,6 +15,7 @@ The **patch** part changes incrmentally at each release.
|
||||||
|
|
||||||
### Changed
|
### Changed
|
||||||
* elasticsearch: use ES_TMPDIR variable for custom tmpdir, (from `/etc/default/elasticsearch` instead of changing `/etc/elesticsearch/jvm.options`).
|
* elasticsearch: use ES_TMPDIR variable for custom tmpdir, (from `/etc/default/elasticsearch` instead of changing `/etc/elesticsearch/jvm.options`).
|
||||||
|
* elasticsearch: RESTART_ON_UPGRADE is configurable (default: `true`)
|
||||||
|
|
||||||
### Fixed
|
### Fixed
|
||||||
* nginx: fix basic auth for default vhost
|
* nginx: fix basic auth for default vhost
|
||||||
|
|
|
@ -20,8 +20,9 @@ Tasks are extracted in several files, included in `tasks/main.yml` :
|
||||||
* `elasticsearch_network_publish_host`: which interface to publish ;
|
* `elasticsearch_network_publish_host`: which interface to publish ;
|
||||||
* `elasticsearch_custom_datadir`: custom datadir ;
|
* `elasticsearch_custom_datadir`: custom datadir ;
|
||||||
* `elasticsearch_custom_tmpdir`: custom tmpdir ;
|
* `elasticsearch_custom_tmpdir`: custom tmpdir ;
|
||||||
* `elasticsearch_jvm_xms`: mininum heap size reserved for the JVM (defaults to 2g).
|
* `elasticsearch_jvm_xms`: mininum heap size reserved for the JVM (default: `2g`).
|
||||||
* `elasticsearch_jvm_xmx`: maximum heap size reserved for the JVM (defaults to 2g).
|
* `elasticsearch_jvm_xmx`: maximum heap size reserved for the JVM (default: `2g`).
|
||||||
|
* `elasticsearch_restart_on_upgrade`: restart the service after package upgrade (default: `true`)
|
||||||
|
|
||||||
By default, Elasticsearch will listen to the public interfaces (`_site_` cf. https://www.elastic.co/guide/en/elasticsearch/reference/5.0/important-settings.html#network.host), so you will have to secure it, with firewall rules for example.
|
By default, Elasticsearch will listen to the public interfaces (`_site_` cf. https://www.elastic.co/guide/en/elasticsearch/reference/5.0/important-settings.html#network.host), so you will have to secure it, with firewall rules for example.
|
||||||
|
|
||||||
|
|
|
@ -11,6 +11,7 @@ elasticsearch_default_tmpdir: /var/lib/elasticsearch/tmp
|
||||||
elasticsearch_jvm_xms: 2g
|
elasticsearch_jvm_xms: 2g
|
||||||
elasticsearch_jvm_xmx: 2g
|
elasticsearch_jvm_xmx: 2g
|
||||||
elasticsearch_log_rotate_days: 365
|
elasticsearch_log_rotate_days: 365
|
||||||
|
elasticsearch_restart_on_upgrade: True
|
||||||
|
|
||||||
elasticsearch_curator: False
|
elasticsearch_curator: False
|
||||||
|
|
||||||
|
|
|
@ -39,12 +39,11 @@
|
||||||
tags:
|
tags:
|
||||||
- config
|
- config
|
||||||
|
|
||||||
- name: Restart on upgrade
|
- name: Configure RESTART_ON_UPGRADE
|
||||||
lineinfile:
|
lineinfile:
|
||||||
dest: /etc/default/elasticsearch
|
dest: /etc/default/elasticsearch
|
||||||
line: "RESTART_ON_UPGRADE=true"
|
|
||||||
regexp: "^RESTART_ON_UPGRADE="
|
regexp: "^RESTART_ON_UPGRADE="
|
||||||
insertafter: "^# *RESTART_ON_UPGRADE=true"
|
insertafter: "^# *RESTART_ON_UPGRADE="
|
||||||
tags:
|
tags:
|
||||||
- config
|
- config
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue