[SERVER-49719] Check that appliedOps oplog entry's field exists in _isTopologyChanged (sharded_backup_restore.js) Created: 18/Jul/20  Updated: 29/Oct/23  Resolved: 21/Jul/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 28

 Description   

Following the introduction - in SERVER-49354 - of a new way of checking for removeShard events in oplog entries, a failure is happening in case no appliedOps field is found in such entries.

A check should be added to check for the existence of the appliedOps key before trying to access it.



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

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-49719 Check that appliedOps oplog entry's field exists in _isTopologyChanged (sharded_backup_restore.js)
Branch: master
https://github.com/mongodb/mongo/commit/b94c216bac4df192aee8de8edee675a837fbf93b

Comment by Githook User [ 21/Jul/20 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-49719 Check that appliedOps oplog entry's field exists in _isTopologyChanged (sharded_backup_restore.js)
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/2e3e9da00a1791d988b9ff5a63a615ea349334d4

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