[SERVER-51011] Determine if tenant migration tests should run on "majority read concern off" Created: 17/Sep/20  Updated: 29/Oct/23  Resolved: 30/Sep/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.8.0

Type: Task Priority: Major - P3
Reporter: Cheahuychou Mao Assignee: Cheahuychou Mao
Resolution: Fixed Votes: 0
Labels: pm-1791_milestone-C
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-10-05
Participants:

 Description   

As described in  SERVER-50456, tenant migration donors need to wait for the write to set the migration state to "committed" and "aborted" to be majority committed. If that is not possible, waitUntilMajorityOpTime inside TenantMigrationAccessBlocker::_waitForOpTimeToMajorityCommit would keep throwing this error so this while loop would cause tests to hang.

This ticket is to determine if tenant migrations should run when enableMajorityReadConcern=false, and why the existing tests do not fail on "majority read concern off". If they should not, we should add the "requires_majority_read_concern” to all tenant migration tests along with a comment explaining why. 



 Comments   
Comment by Githook User [ 30/Sep/20 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}

Message: SERVER-51011 Determine if tenant migration tests should run on "majority read concern off"
Branch: master
https://github.com/mongodb/mongo/commit/d8d30d268bfccc2bfd646d45bc2e339742c3a0ea

Generated at Thu Feb 08 05:24:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.