[FEAT] 🟢 Phase 3: Dual Write Setup (Weeks 9-10)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Description
Goal: Deploy 3.x cluster, reindex data, enable dual-write synchronization
Timeline: 2 weeks
Business Impact: None - still reading from 1.0 only
Status: 📋 Planned
Desired Outcome
Business Outcome:
Customers continue to experience the same search performance and results they always have. At the same time, we build a new OpenSearch 3.x infrastructure foundation that runs invisibly in parallel with zero customer impact.
Technical Outcome:
A fully operational OpenSearch 3.x cluster containing all data from the OpenSearch 1.0 cluster with <1 second synchronization lag, validated through automated integrity checks, while all customer traffic continues to read exclusively from the proven 1.0 infrastructure.
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
No files, tests, or entry points are identified in the issue. Start by locating the existing OpenSearch 1.0 deployment and data indexing paths, then define how reindexing, dual-write synchronization, and integrity checks will be implemented and validated without changing customer reads.
Written by the indexing model from the issue text.
Assessment
- Domain
- data, infrastructure, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100