[SERVER-74364] Run periodic noop writer in nodes_in_primarys_datacenter_dont_sync_across_datacenters.js Created: 24/Feb/23  Updated: 29/Oct/23  Resolved: 28/Feb/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Samyukta Lanka Assignee: Samyukta Lanka
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 2023-03-06
Participants:
Linked BF Score: 5

 Description   

During the test, we expect a node to switch its sync source to be the primary. The test times out waiting for this to happen, but the node is never able to sync from the expected node since it isn't eligible. It looks like node 1 denylists the primary due to network issues, but by the time it re-evaluates the primary as a sync source, it has already caught up to it.

The periodic noop writer should mean that the primary will keep advancing its optime, so it will be an eligible sync source after such network issues.



 Comments   
Comment by Githook User [ 27/Feb/23 ]

Author:

{'name': 'Samy Lanka', 'email': 'samy.lanka@mongodb.com', 'username': 'lankas'}

Message: SERVER-74364 Run periodic noop writer in nodes_in_primarys_datacenter_dont_sync_across_datacenters.js
Branch: master
https://github.com/mongodb/mongo/commit/4cdd0e87051285b94b5b809a67aa35146d57dd51

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