[SERVER-11709] Correctly handle applyOps command as part of role graph updating Created: 14/Nov/13  Updated: 11/Jul/16  Resolved: 15/Nov/13

Status: Closed
Project: Core Server
Component/s: Security
Affects Version/s: 2.5.4
Fix Version/s: 2.5.4

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Andy Schwerin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Currently when an applyOps op is processed by logOp(), the following error is logged:
ERROR: Unsupported modification to roles collection in oplog; TODO how to remedy. OplogOperationUnsupported Unsupported oplog operation Oplog entry: c

Instead, the behavior needs to be that the role graph system parses the command and responds to anything that changes role data.



 Comments   
Comment by Githook User [ 15/Nov/13 ]

Author:

{u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@10gen.com'}

Message: SERVER-11709 RoleGraph should ignore oplog entries for the applyOps command.

The individual operations in the command will be separately applied, so there's nothing for the RoleGraph to do with the applyOps command itself.

Includes an integration test of role replication.
Branch: master
https://github.com/mongodb/mongo/commit/1d9e58d26bfbd14663d18eab4504bb295a22d90e

Generated at Thu Feb 08 03:26:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.