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

Elasticsearch migration from 5.6 to 6.8 #1813

Open
wants to merge 33 commits into
base: master
Choose a base branch
from

Conversation

jphilou
Copy link
Contributor

@jphilou jphilou commented Jun 11, 2024

ElasticSearch Upgrade from v5.6 to V6.8 for docker env. like dev one.

The docker-compose file has been updated in order to facilitate and automotive plugins installation and prepare the environment for migration.
The ElasticSearch 5.6 is still build and run but would not be the main ES for the service. It could be decommissioned after migration.
docker-compose file contains as well :

  • api building with integration of the requirements.txt for python pip installation (component updates)
  • ES 5.6 listening on port 9201 instead of 9200 : > elasticsearch26
  • redis no change
  • postgresql no change
  • ES 6.8 listening on port 9200 and 9300 (elasticsearch6.Dockerfile) > elasticsearch
  • Logstash 6.8 for data migration purpose. (logstash6.Dockerfile)

migration steps

  1. build the environment : docker-compose build
  2. Launch the environment : docker-compose up -d
  3. Create the index and its mapping : ./scripts/esUpdateMappings56.sh
  4. Data Migration : docker-compose start logstash6 It will stop by itself when migration would be achieved
  5. postgresql shema up to date: docker-compose exec api .build/venv/bin/alembic upgrade head

post migration

if all the process has been passed without issues. you can comment or remove in the docker-compose.yml services :

  • logstash
  • elasticsearch56

jphilou and others added 30 commits May 7, 2024 19:41
add a step in order to install the elasticsearch plugin in order to pass cover tests.
Test de création de la branch remote sur un texte sans impact.
- Mapping Update (scripts and code)
- Code update for deprecation update (fields, missings, ...)
- Component update (elasticsearch, elasticsearch DSL)
- Migration scripts and logstash engine / pipeline
- CI scripts
- Mapping Update (scripts and code)
- Code update for deprecation update (fields, missings, ...)
- Component update (elasticsearch, elasticsearch DSL)
- Migration scripts and logstash engine / pipeline
- CI scripts
- Mapping Update (scripts and code)
- Code update for deprecation update (fields, missings, ...)
- Component update (elasticsearch, elasticsearch DSL)
- Migration scripts and logstash engine / pipeline
- CI scripts
- Mapping Update (scripts and code)
- Code update for deprecation update (fields, missings, ...)
- Component update (elasticsearch, elasticsearch DSL)
- Migration scripts and logstash engine / pipeline
- CI scripts
CI:
- retirer dans l'installation de ES 5.6 les paramètres inconsistant
+ install plugin analysis-icu sur ES
CI:
- retirer dans l'installation de ES 5.6 les paramètres inconsistant
+ install plugin analysis-icu sur ES
Script de création / mapping / settings des indices ES
- CI/CD : ES Download version
…-to-6.8' into elasticsearch-migration-from-5.6-to-6.8
jphilou added 3 commits June 11, 2024 12:09
- Update settings es in config file for github-actions
- test_fill_index fix coquille
Copy link

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
-0.02% 92.27%
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (24e010e) 19853 18407 92.72%
Head commit (ce8c934) 19934 (+81) 18479 (+72) 92.70% (-0.02%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#1813) 194 179 92.27%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences


🚀 Don’t miss a bit, follow what’s new on Codacy.

Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more

@jphilou jphilou self-assigned this Jun 18, 2024
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

Successfully merging this pull request may close these issues.

1 participant