artefactual-labs / ansible-elasticsearch Goto Github PK

https://www.elastic.co/guide/en/elasticsearch/guide/1.x/_limiting_memory_usage.html#fielddata-size

https://securelist.com/cve-2021-44228-vulnerability-in-apache-log4j-library/105210/
https://access.redhat.com/security/cve/CVE-2021-4104

To avoid problems, we should bind to localhost by default

There's no variable in template to configure path.repo. We are using it for backups and AtoM replication script. The setting is added by a separate playbook.

The problem is when running this role again: the path.repo setting is lost.

Including this new variable in template will fix the issue.

Oracle repository seems to be no longer providing the
oracle-java8-installer package required by this role by default, producing an error and breaking the apt installer (subsequent apt-get commands issue keep trying to install it)

Workaround:

• do a dpkg -r oracle-java8-installer on the affected machine to fix apt
• Install openjdk instead of oracle java (ref. #3), see artefactual/deploy-pub#47 for an example

Hello,

What is the purpose of deleting and recreating the plugin directory?

Thanks!

openjdk-jre-7-headless is available in 14.04
openjdk-jre-{8,9}-headless available in 16.04

After merging #19, when installing elasticsearch 5 with default options it fails because the following options don't exist in ES 5, they are ES 6 variables:

https://github.com/artefactual-labs/ansible-elasticsearch/pull/19/files#diff-7eeda618087b49ae876084ab6c73fdbbR41-R42

ES 5 must use:

- "thread_pool.bulk.size: 2"
- "thread_pool.bulk.queue_size: 1000"

AtoM 2.5 needs Elasticsearch 5.x.

Several changes are needed to upgrade to Elasticsearch 5.x with this ansible role. Upgrading is not about just changing the variable elasticsearch_version to '5.X.Y' version and running the role.