[DOCS-12994] Investigate changes in SERVER-43045: dbhash does not hash all replicated collections Created: 29/Aug/19  Updated: 13/Nov/23

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: 4.3 Required, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-43045 dbhash does not hash all replicated c... Closed
Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-12974

 Description   

Description

Downstream Change Summary

null

Description of Linked Ticket

Its way of determining if a namespace is replicated is wrong and stale.

Scope of changes

  • what is the previous behavior of dbhash
  • What is the new behavior of dbhash
  • DO we need to backport the previous behavior of dbhash

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Comment by Judah Schvimer [ 23/Sep/20 ]

Hashing is done uniformly across the set, however the collections we hash did change on upgrade. I'm not sure if that warrants documentation, I would expect so, but I'm not sure.

Comment by Judah Schvimer [ 29/Aug/19 ]

I reopened SERVER-43045 to handle mixed version concerns using FCV, rather than just in our tests, which should hopefully limit downstream impact.

Generated at Thu Feb 08 08:06:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.