[SERVER-69700] Replication rollback fails resharding_coordinator_recovers_abort_decision.js Created: 14/Sep/22  Updated: 29/Oct/23  Resolved: 21/Sep/22

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.0.14, 6.0.3, 6.1.0-rc4, 6.2.0-rc0

Type: Bug Priority: Major - P3
Reporter: Abdul Qadeer Assignee: Abdul Qadeer
Resolution: Fixed Votes: 0
Labels: sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v6.1, v6.0, v5.0
Sprint: Sharding 2022-09-19, Sharding 2022-10-03
Participants:
Linked BF Score: 35
Story Points: 1

 Description   

In BF-26341, the following can be observed in logs:

 

[js_test:resharding_coordinator_recovers_abort_decision] c20296| 2022-09-11T05:28:13.563+00:00 I  REPL     21098   [BackgroundSync] "Starting rollback due to fetcher error","attr":{"error":"OplogStartMissing: the sync source's oplog and our oplog have diverged, going into rollback. our last optime fetched: { ts: Timestamp(1662874093, 2), t: 1 }. optime of first document in batch: { ts: Timestamp(1662874093, 4), t: 2 }. sync source's first optime: { ts: Timestamp(1662874088, 18), t: 1 }","lastCommittedOpTime":{"ts":{"$timestamp":{"t":1662874092,"i":42}},"t":1}}
...
...
[js_test:resharding_coordinator_recovers_abort_decision] c20297| 2022-09-11T05:28:13.980+00:00 I  REPL     21105   [BackgroundSync] "Rollback successful"

This causes the test client disconnection and the command to turn off the failpoint fails. A fix here would be to wait for secondaries to be ready before doing so.

 



 Comments   
Comment by Githook User [ 27/Sep/22 ]

Author:

{'name': 'Abdul Qadeer', 'email': 'abdul.qadeer@mongodb.com', 'username': 'zorro786'}

Message: SERVER-69700 Await secondaries' readiness

(cherry picked from commit 6eaf0ea0d0bf24a0d7cfe97c7de7070b3b1baa7e)
Branch: v5.0
https://github.com/mongodb/mongo/commit/a2bde0ebc259bf57218f16baa9f8d2a4cbb789e4

Comment by Githook User [ 27/Sep/22 ]

Author:

{'name': 'Abdul Qadeer', 'email': 'abdul.qadeer@mongodb.com', 'username': 'zorro786'}

Message: SERVER-69700 Await secondaries' readiness

(cherry picked from commit 6eaf0ea0d0bf24a0d7cfe97c7de7070b3b1baa7e)
Branch: v6.1
https://github.com/mongodb/mongo/commit/2af7b4b1a2439308ba4b2fc6596c0cc03ff99b55

Comment by Githook User [ 27/Sep/22 ]

Author:

{'name': 'Abdul Qadeer', 'email': 'abdul.qadeer@mongodb.com', 'username': 'zorro786'}

Message: SERVER-69700 Await secondaries' readiness

(cherry picked from commit 6eaf0ea0d0bf24a0d7cfe97c7de7070b3b1baa7e)
Branch: v6.0
https://github.com/mongodb/mongo/commit/304ce9043ce71b8fc1ec45a2c31d4410df33769f

Comment by Githook User [ 21/Sep/22 ]

Author:

{'name': 'Abdul Qadeer', 'email': 'abdul.qadeer@mongodb.com', 'username': 'zorro786'}

Message: SERVER-69700 Await secondaries' readiness
Branch: master
https://github.com/mongodb/mongo/commit/6eaf0ea0d0bf24a0d7cfe97c7de7070b3b1baa7e

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