[SERVER-70686] remainingInitialSyncEstimatedMillis progresses through negative values Created: 19/Oct/22  Updated: 20/Nov/23  Resolved: 14/Aug/23

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

Type: Bug Priority: Major - P3
Reporter: Enrique Garnelo Prediger Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-53017 replSetGetStatus remainingInitialSync... Closed
Assigned Teams:
Replication
Operating System: ALL
Steps To Reproduce:
  1. Create a Replica Set on 4.4.17 with at least 3 members. 
  2. Load it with a large amount of data
  3. Perform an initial sync on one of the secondaries
  4. Keep adding data to the primary in a constant manner
  5. Check for remainingInitialSyncEstimatedMillis from replica set status
Participants:

 Description   

Observed in MongoDB Server 4.4.17 with a node in ST2. 

The value for remainingInitialSyncEstimatedMillis goes to negative values:

 "remainingInitialSyncEstimatedMillis": -4589051,

The expected behaviour would be to adjust the estimation as it progresses to determine if the original was actually accurate. 



 Comments   
Comment by Samyukta Lanka [ 24/Oct/22 ]

This is the first time we've seen this since 4.4 is released, we expect this is pretty rare. If this is causing a lot of pain, please reopen.

CC alan.zheng@mongodb.com

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