[SERVER-31662] Initialize rbid to 1 and log when it changes Created: 20/Oct/17  Updated: 30/Oct/23  Resolved: 28/Nov/17

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

Type: Bug Priority: Major - P3
Reporter: Judah Schvimer Assignee: William Schultz (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
related to SERVER-32776 Refresh rollback id cache on increment Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.6
Sprint: Repl 2017-12-04
Participants:
Linked BF Score: 0

 Description   

Due to a 3.4 bug, certain versions can invariant if they go through sync source selection during RECOVERING post rollback and receive an rbid of 0. One way to reduce the chance of this happening is to initialize the rbid to 1 in 3.6.

We should also log the rbid clearly whenever it changes so we know what to expect it to be.



 Comments   
Comment by Githook User [ 11/Dec/17 ]

Author:

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

Message: SERVER-31662 Initialize rollback id to 1 and log when it changes

(cherry picked from commit 48c4e4eb48e7994a78bee8f3384df2963a1ea407)
Branch: v3.6
https://github.com/mongodb/mongo/commit/5b7d52009c42ed963c9eb98c36edb9f96f4d8319

Comment by Githook User [ 28/Nov/17 ]

Author:

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

Message: SERVER-31662 Initialize rollback id to 1 and log when it changes
Branch: master
https://github.com/mongodb/mongo/commit/48c4e4eb48e7994a78bee8f3384df2963a1ea407

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