[SERVER-33946] Decrease number of initial sync attempts in tests to 1 Created: 01/Feb/18  Updated: 06/Dec/22

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

Type: Task Priority: Major - P3
Reporter: Siyuan Zhou Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: former-robust-initial-sync
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-7515 idempotence violation when intermedia... Open
depends on SERVER-27357 Recreating collection with different ... Backlog
depends on SERVER-32225 Initial sync should ignore multiple t... Closed
depends on SERVER-32903 Ambiguous field name error should be ... Closed
depends on SERVER-33956 A sequence of rename and create colle... Closed
depends on SERVER-44462 Run listIndexes with a single snapsho... Closed
depends on SERVER-33060 Increase initial sync attempts in ini... Closed
depends on SERVER-27122 Restart initial sync for known index ... Backlog
Related
Assigned Teams:
Replication
Participants:
Linked BF Score: 45

 Description   

This ticket is to track the idemponecy failures we found in BF's after reducing the initial sync attempts to 1 in SERVER-31093.



 Comments   
Comment by Judah Schvimer [ 06/Nov/19 ]

This should only actually depend on SERVER-27122, and then we can do all of the rest of the idempotency fixes to reduce the number of known idempotency problems. Until that is complete, we can keep the links as they are today.

Comment by Siyuan Zhou [ 16/Mar/18 ]

Moved this ticket to SERVER. I suggest putting it into Backlog to track remaining idempotency issues.

Comment by Siyuan Zhou [ 02/Mar/18 ]

spencer, after SERVER-33060, the problems linked in this ticket got masked, but they are still legitimate issues IMO. This ticket is used to track those failures and bugs. I still want a ticket to track all of them if it's not a BF ticket, either a SERVER ticket or a PM ticket?

Comment by Spencer Brody (Inactive) [ 02/Mar/18 ]

siyuan.zhou, what's the status of this ticket? Can this be closed now?

Comment by Max Hirschhorn [ 03/Feb/18 ]

The number of initial sync attempts has been increased back to 10 with the change from 3a5d38b as part of SERVER-33060. siyuan.zhou, spencer, I think after the Replication team is done cataloguing the outstanding idempotency issues with initial sync, all of the BF tickets that failed during the replica_sets_initsync_jscore_passthrough Evergreen task (e.g. not BF-7860) should be resolved as "Fixed" by depending on SERVER-33060. I filed TIG-742 as a workaround for the $text index issue we've seen in the fuzzer and would suggest similar other workarounds be requested.

Comment by Siyuan Zhou [ 01/Feb/18 ]

One solution is to increase the initial sync attempts again.

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