[FEAT] 🔴 Phase 6: Write Cutover (Week 16)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Description
Goal: Make 3.x primary for reads and writes, shadow write to 1.0 for safety
Timeline: 1 week
Business Impact: None if successful - transparent
Status: 📋 Planned
Desired Outcome
Business Outcome:
OpenSearch 3.x becomes the production system of record for all search operations while maintaining the proven 1.0 cluster as a synchronized backup, giving customers a modern, supported search infrastructure with continued zero downtime and the safety of instant rollback capability.
Technical Outcome:
All write operations (index, update, delete) successfully migrated to OpenSearch 3.x cluster as primary, with shadow writes to 1.0 cluster for safety, achieving <1 second write latency and 100% write success rate while maintaining ability to revert to 1.0 as primary within minutes if issues arise.
Target Personas
- Developer teams
- Content teams
- DevOps teams
- System administrators (dotCMS)
Links
No response
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
The issue provides no files, tests, or entry points to follow. Start by locating the existing OpenSearch migration and write-operation paths, then verify that 3.x is primary, writes are shadowed to 1.0, latency and success targets are met, and rollback remains possible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, devops, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100