[SERVER-17934] Do not report upstream progress while in state STARTUP2 Created: 08/Apr/15  Updated: 28/Feb/20  Resolved: 28/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: Matt Dannenberg Assignee: Vesselina Ratcheva (Inactive)
Resolution: Done Votes: 0
Labels: datarepl3.2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-45997 Test re-sync cases where nodes can ro... Closed
Documented
is documented by DOCS-13463 Investigate changes in SERVER-17934: ... Closed
Duplicate
is duplicated by SERVER-32237 Nodes that cannot become primary must... Closed
Related
related to SERVER-19244 Secondary position information can be... Closed
is related to SERVER-18511 Report upstream progress when initial... Closed
is related to SERVER-45995 Test that nodes in initial sync maint... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2020-02-24, Repl 2020-03-09
Participants:
Linked BF Score: 0

 Description   

Another way to look at this is that we should only report if we are secondary, and report when we become secondary in addition.



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

Author:

{'username': 'vessy-mongodb', 'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com'}

Message: SERVER-17934 Do not report replication progress upstream while in initial sync

This reverts commit fe919dd89cee7de435aa58984ff1dd940fee839e.
Branch: master
https://github.com/mongodb/mongo/commit/e41ba31d3e77f79fb4c110dc593bd09cfc0cee20

Comment by Githook User [ 27/Feb/20 ]

Author:

{'name': 'William Schultz', 'username': 'will62794', 'email': 'william.schultz@mongodb.com'}

Message: Revert "SERVER-17934 Do not report replication progress upstream while in initial sync"

This reverts commit 3230c16349387faaee28efe830573c2e6076789a.

delete mode 100644 jstests/replsets/no_progress_updates_during_initial_sync.js
Branch: master
https://github.com/mongodb/mongo/commit/fe919dd89cee7de435aa58984ff1dd940fee839e

Comment by William Schultz (Inactive) [ 27/Feb/20 ]

Looks like the commit's test is still failing every time. Going to revert.

Comment by Githook User [ 27/Feb/20 ]

Author:

{'name': 'Vesselina Ratcheva', 'username': 'vessy-mongodb', 'email': 'vesselina.ratcheva@10gen.com'}

Message: SERVER-17934 Do not report replication progress upstream while in initial sync
Branch: master
https://github.com/mongodb/mongo/commit/3230c16349387faaee28efe830573c2e6076789a

Comment by Githook User [ 26/Feb/20 ]

Author:

{'username': 'vessy-mongodb', 'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com'}

Message: Revert "SERVER-17934 Do not report replication progress upstream while in initial sync"

This reverts commit c87d505f571c7dbe45048cd3cbe116278f8efa31.
Branch: master
https://github.com/mongodb/mongo/commit/8651c754eedf84651dd5051aa43c70cd96b00586

Comment by Githook User [ 26/Feb/20 ]

Author:

{'name': 'Vesselina Ratcheva', 'username': 'vessy-mongodb', 'email': 'vesselina.ratcheva@10gen.com'}

Message: SERVER-17934 Do not report replication progress upstream while in initial sync
Branch: master
https://github.com/mongodb/mongo/commit/c87d505f571c7dbe45048cd3cbe116278f8efa31

Generated at Thu Feb 08 03:46:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.