-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Tools and Replicator
-
14
Problem Statement/Rationale
Due to TOOLS-1818, mongodump currently has a guardrail that forbids any change to the admin.system.version namespace when doing an oplog dump. According to the ticket description, the guardrail was added to prevent FCV changes during an oplog dump, and might also be used to prevent moveChunk operations. However, this is also giving an error when operations change users / roles / privileges.
Steps to Reproduce
- Start mongodump with --oplog option
- Run an operation to create / update a user, role or privilege
Expected Results
It's unclear whether this should be supported.
Actual Results
Mongodump fails with the following error:
Failed: error dumping oplog: error writing data for collection `.oplog` to disk: cannot dump with oplog if admin.system.version is modified by {"op": "i","ns": "admin.system.version","ui": {"$binary":{"base64":"AvZ+LL5CTJWBpm2pD1aONw==","subType":"04"}},"o": {"_id": "authSchema","currentVersion": {"$numberInt":"5"}},"ts": {"$timestamp":{"t":1769113144,"i":107}},"t": {"$numberLong":"1"},"v": {"$numberLong":"2"},"wall": {"$date":{"$numberLong":"1769113144453"}}}
Additional Notes
The bug is found in a passthrough BF (TOOLS-4054)
- is related to
-
TOOLS-1818 Abort dump if feature compatibility version changes
-
- Closed
-
-
TOOLS-4054 cannot dump with oplog if admin.system.version is modified | failed: ctc_rs_dump_oplog_sleep_jscore_passthrough_v44_to_v44 on mongodump-v44-to-v44-amazon2-arm64 [mongo-tools @ 3f2e10ee] (job_log_job2)
-
- In Code Review
-