[SERVER-42454] Wait for node to find appropriate sync source before disabling failpoint in do_not_advance_commit_point_beyond_last_applied_term.js Created: 26/Jul/19  Updated: 29/Oct/23  Resolved: 01/Aug/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.0.13, 4.2.1, 4.3.1

Type: Bug Priority: Major - P3
Reporter: Jason Chan Assignee: Jason Chan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
is related to SERVER-41081 do_not_advance_commit_point_beyond_la... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2, v4.0
Sprint: Repl 2019-08-12
Participants:
Linked BF Score: 16

 Description   

Currently, the stopReplProducerOnDocument failpoint ignores and silently fails the batch of downloaded operations. In most cases, we expect the document that triggers the failpoint should never be applied. However, since we continue to receive responses from the fetcher even when the failpoint is enabled, it is possible that a fetcher response is already in the middle of being processed when we disable the failpoint. This can lead to a document to be applied when we don't expect it to.

In do_not_advance_commit_point_beyond_last_applied_term.js, it is possible that we end up replicating the term 3 document onto node E which we don't expect, this causes node B to sync from node E which our test doesn't account for. We should instead wait for node E to sync from node B before disabling the stopReplProducerOnDocument failpoint.



 Comments   
Comment by Githook User [ 19/Aug/19 ]

Author:

{'name': 'Jason Chan', 'email': 'jason.chan@10gen.com', 'username': 'jasonjhchan'}

Message: SERVER-42454 Wait for node to find appropriate sync source before disabling failpoint in do_not_advance_commit_point_beyond_last_applied_term.js

(cherry picked from commit 5e6cf8abca43a19b8634afd68343a933545d8a22)
Branch: v4.2
https://github.com/mongodb/mongo/commit/141e7d0f6c85c2454d349769b0b878748cc03926

Comment by Githook User [ 13/Aug/19 ]

Author:

{'name': 'Jason Chan', 'email': 'jason.chan@10gen.com', 'username': 'jasonjhchan'}

Message: SERVER-42454 Wait for node to find appropriate sync source before disabling failpoint in do_not_advance_commit_point_beyond_last_applied_term.js

(cherry picked from commit 5e6cf8abca43a19b8634afd68343a933545d8a22)
Branch: v4.0
https://github.com/mongodb/mongo/commit/97b3471d5a176bf0cb2be20f6c82ff65f6df2944

Comment by Githook User [ 01/Aug/19 ]

Author:

{'name': 'Jason Chan', 'username': 'jasonjhchan', 'email': 'jason.chan@10gen.com'}

Message: SERVER-42454 Wait for node to find appropriate sync source before disabling failpoint in do_not_advance_commit_point_beyond_last_applied_term.js
Branch: master
https://github.com/mongodb/mongo/commit/5e6cf8abca43a19b8634afd68343a933545d8a22

Generated at Thu Feb 08 05:00:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.