[SERVER-4259] must a failure of applyOperation_inlock() be handled in ApplyOpsCmd? Created: 11/Nov/11  Updated: 11/Jul/16  Resolved: 13/Feb/12

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

Type: Bug Priority: Major - P3
Reporter: Dwight Merriman Assignee: Kristina Chodorow (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-3956 A new replica secondary may be missin... Closed
related to DOCS-133 Document applyOps Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

ApplyOpsCmd calls applyOperation_inlock() but does not return the result code. Is there an issue analogous to SERVER-3956 initial sync in replication?

Also the same question for

  • cloning a collection or database using those commands;
  • mongodump using oplog


 Comments   
Comment by auto [ 13/Feb/12 ]

Author:

{u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}

Message: Added array of success/failures to applyOps output SERVER-4259
Branch: master
https://github.com/mongodb/mongo/commit/23cbe7d09c0370d61367c1da65ab4a944370edd1

Comment by Eliot Horowitz (Inactive) [ 11/Nov/11 ]

We should return an array of passes/fails.

This is currently only used for sharding splits, where all pre and post conditions are checked, so no issues today.

But if this command becomes more used, might happen.

Comment by auto [ 11/Nov/11 ]

Author:

{u'login': u'dwight', u'name': u'dwight', u'email': u'dwight@10gen.com'}

Message: SERVER-4259 comment
Branch: master
https://github.com/mongodb/mongo/commit/bad807e45b26856cafd583bfbaa7f8dbb13a9c6d

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