[EPIC] 🟢 OpenSearch Upgrade Rollout
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Description
This EPIC covers the rollout of OpenSearch upgrade for dotCMS using a phased, zero-downtime migration strategy. The upgrade ensures continuity of search functionality while transitioning from the existing search infrastructure to OpenSearch through careful orchestration of dual writes, shadow reads, traffic migration, and eventual cutover.
Desired Outcome
- Successful migration to OpenSearch with zero downtime
- All search operations functioning correctly on the new infrastructure
- Old search infrastructure safely decommissioned
- Performance metrics show equal or better performance compared to the previous system
Target Personas
- DevOps teams
- System administrators (dotCMS)
Links
- Related phases tracked as sub-issues in this EPIC
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the related phase sub-issues, since this epic does not name implementation files, tests, or entry points. Review how the phased migration covers dual writes, shadow reads, traffic migration, cutover, and decommissioning; done means zero-downtime search on OpenSearch with equal or better performance and the old infrastructure safely removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devops, infrastructure, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100