[SERVER-45926] Tag server_status_metrics.js requires_document_locking Created: 03/Feb/20  Updated: 29/Oct/23  Resolved: 03/Feb/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.3.4

Type: Bug Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Lingzhi Deng
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2020-02-10
Participants:
Linked BF Score: 44

 Description   

The new test added in SERVER-44711 for metrics.repl.network.oplogGetMoresProcessed requires_document_locking. This is because the test blocks oplog fetching on a failpoint while trying to do oplog writes. Under ephemeralForTest, the oplog writes (acquiring X lock) would conflict with the oplog reads (holding S lock) that's blocked on a failpoint.

Normally that's not a problem because oplog writes should take MODE_IX locks and oplog reads should take MODE_IS when the storage engine supports document level locking.



 Comments   
Comment by Githook User [ 03/Feb/20 ]

Author:

{'name': 'Lingzhi Deng', 'username': 'ldennis', 'email': 'lingzhi.deng@mongodb.com'}

Message: SERVER-45926: Tag server_status_metrics.js requires_document_locking
Branch: master
https://github.com/mongodb/mongo/commit/8f1168579321f2a04d7f1cc3ee8a93f15676b40d

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