[SERVER-48628] Out of order oplog application for transactions that create a collection with malformed name Created: 05/Jun/20  Updated: 29/Oct/23  Resolved: 08/Jul/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.4.0-rc14, 4.7.0

Type: Bug Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Eric Milkie
Resolution: Fixed Votes: 0
Labels: None
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:
v4.4
Sprint: Execution Team 2020-06-29, Execution Team 2020-07-13
Participants:
Linked BF Score: 6

 Description   

The documentation says: "Collection names should begin with an underscore or a letter character". But looks like it is not enforced. I think we should either disallow creating collection with such names or avoid crashing the secondary oplog application.



 Comments   
Comment by Githook User [ 11/Jul/20 ]

Author:

{'name': 'Eric Milkie', 'email': 'milkie@10gen.com', 'username': 'milkie'}

Message: SERVER-48628 sort oplog entries first in applier batches, for create ops in transactions

(cherry picked from commit 13d756e1645f3d41439f336d2312777dd0cb1999)
Branch: v4.4
https://github.com/mongodb/mongo/commit/383e442b881c089afebaea1d11aeec196f8efc56

Comment by Githook User [ 08/Jul/20 ]

Author:

{'name': 'Eric Milkie', 'email': 'milkie@10gen.com', 'username': 'milkie'}

Message: SERVER-48628 sort oplog entries first in applier batches, for create ops in transactions
Branch: master
https://github.com/mongodb/mongo/commit/13d756e1645f3d41439f336d2312777dd0cb1999

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