[SERVER-13357] 'clone' command cannot be run against a secondary Created: 26/Mar/14  Updated: 10/Nov/15  Resolved: 20/Feb/15

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.6.0-rc2
Fix Version/s: 3.1.0

Type: Bug Priority: Major - P3
Reporter: Matt Dannenberg Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: RPL 0 3/13/15
Participants:

 Description   

You cannot set slaveOk on the connection between the server and the secondary from which it would clone the database.

There is testing in place for this in jstests/replsets/cloneDb.js, which should be uncommented upon completion of this ticket.



 Comments   
Comment by Githook User [ 23/Feb/15 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-13357 fix replset/cloneDb.js
Branch: master
https://github.com/mongodb/mongo/commit/aff9fedac8a1f79db0a42ddae6ce80b5f6cb0805

Comment by Githook User [ 20/Feb/15 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-13357 add slaveOk argument to clone
Branch: master
https://github.com/mongodb/mongo/commit/56202c537bfa6de56ca98d8caa04eaf095b7ef62

Comment by Eric Milkie [ 20/Feb/15 ]

I believe we just need to set opts.slaveOk for the clone command's use of the cloner.

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