Operational Defect Database
BugZero found this defect 83 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2589800
Chunk refresh from a secondary does not wait for majority writeConcern while flushing
Last update date:
3/14/2024
Affected products:
MongoDB Server
Affected releases:
7.0.6
5.0.25
4.4.29
6.0.14
7.3.0-rc3
Fixed releases:
8.0.0-rc0
Description:
Info
Consider the following scenario: Secondary schedules a refresh of the chunks on the primary Primary successfully writes the refresh locally Before this operation gets replicated and we advance the stable timestamp we stepDown the primary As a result of this, since the new primary will not be inclusive of the refresh the returned opTime is completely meaninglesss since it will be associated to arolled back entry.
Top User Comments
xgen-internal-githook commented on Wed, 13 Mar 2024 10:40:53 +0000: Author: {'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'} Message: SERVER-87058 Fail catalog flushes if replication state has changed between start and finish (#19293) GitOrigin-RevId: d19a372790e7f4a2ad8c565d924f056732c2f323 Branch: master https://github.com/mongodb/mongo/commit/43abd7d3ff900669cc7c744c22a1423784bd4c6d
Steps to Reproduce
