Summary: | ElasticSearch 7 start crash: at least one of [discovery.seed_hosts, discovery.seed_providers, cluster.initial_master_nodes] must be configured | ||
---|---|---|---|
Product: | Koha | Reporter: | Victor Grousset/tuxayo <victor> |
Component: | Searching - Elasticsearch | Assignee: | Bugs List <koha-bugs> |
Status: | RESOLVED MOVED | QA Contact: | |
Severity: | critical | ||
Priority: | P5 - low | CC: | jonathan.druart, kevin.carnes |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: | ||
Bug Depends on: | |||
Bug Blocks: | 25439 | ||
Attachments: | Bug 25684: ElasticSearch 7 start crash: at least one of [discovery.seed_hosts, discovery.seed_providers, cluster.initial_master_nodes] must be configured |
Description
Victor Grousset/tuxayo
2020-06-06 03:19:24 UTC
Odd, ES6 doesn't do a deprecation warning about this. I though it worked like that so there would never be a bad surprise when upgrading to a major version. Adding "- discovery.type=single-node" under environment in docker-compose.es7.yml fixed the problem for me. Created attachment 130289 [details] [review] Bug 25684: ElasticSearch 7 start crash: at least one of [discovery.seed_hosts, discovery.seed_providers, cluster.initial_master_nodes] must be configured With Elasticsearch 7 it is necessary to specify if using a single node To test: 1) run ku-es7 2) Observe that Elasticsearch stops with an error 3) Apply patch 4) run ku-es7 5) Observe that Elasticsearch starts successfully 6) Sign off Sponsored-by: Lund University Library Great so it's not a Koha problem! It's about koha-testing-docker, the repository is there: https://gitlab.com/koha-community/koha-testing-docker So the patch must be submitted there Confirmed to be working :) |