dotCMS / dotCMS/core

[FEAT] 🟡 Phase 4: Shadow Reads (Weeks 11-12)

Open
#33,951 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Epic OpenSearch stale Team : Scout
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Description

Goal: Query both clusters, compare results, and customers see only 1 result
Timeline: 2 weeks
Business Impact: None - shadow testing only
Status: 📋 Planned

Desired Outcome

Business Outcome:

Customers continue to receive fast, accurate search results from the proven 1.0 cluster while we comprehensively validate that the 3.x cluster produces identical results, building confidence that the new infrastructure is production-ready.

Technical Outcome:

Every search query sent to production is simultaneously executed against both OpenSearch 1.0 and 3.x clusters with results compared in real-time, achieving >99.9% parity and identifying any discrepancies before customer traffic is routed to 3.x, with all differences documented and resolved or accepted.

Target Personas
  • Developer teams
  • Content teams
  • DevOps teams
  • System administrators (dotCMS)
Links

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by locating the production search request path and the configuration for the OpenSearch 1.0 and 3.x clusters. Done means production queries reach both clusters, customers receive only the proven result, comparisons identify discrepancies, and parity exceeds 99.9% with differences documented and resolved or accepted.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, distributed-systems, search
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.