[SERVER-3854] mongodump 2.0.0 fails on replica/slave Created: 14/Sep/11  Updated: 11/Jul/16  Resolved: 23/Sep/11

Status: Closed
Project: Core Server
Component/s: Tools
Affects Version/s: 2.0.0
Fix Version/s: 2.0.1, 2.1.0

Type: Bug Priority: Major - P3
Reporter: Reed O'Brien Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

build info: Linux bs-linux64.10gen.cc 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_41

OS info: Linux emma 2.6.38-10-server #46-Ubuntu SMP Tue Jun 28 16:31:00 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux


Issue Links:
Depends
Duplicate
is duplicated by SERVER-3904 mongodump fails with version 2.0.0 in... Closed
Operating System: ALL
Participants:

 Description   

robrien@emma:~/tmp/cam/build$ mongodump --version
mongodump version 2.0.0
robrien@emma:~/tmp/cam/build$ mongod --version
db version v2.0.0, pdfile version 4.5
Wed Sep 14 14:32:00 git version: 695c67dff0ffc361b8568a13366f027caa406222

With the above versions on a replica slave mongodump exits with an error:
robrien@emma:~/tmp/cam/build$ mongodump
connected to: 127.0.0.1
all dbs
assertion: 13106 nextSafe():

{ $err: "not master and slaveok=false", code: 13435 }

 Comments   
Comment by Krzysztof Wilczynski [ 27/Oct/11 ]

2.0.1 already in production! Thank you guys!

KW

Comment by Spencer Brody (Inactive) [ 18/Oct/11 ]

2.0.1-rc1 just went out. The official 2.0.1 release should be very soon - most likely either the end of this week or early next week.

Comment by Krzysztof Wilczynski [ 17/Oct/11 ]

I am using binary from 1.8.x for the time being.

+1 for the idea

P.S. I see that 2.0.1 is due "tomorrow"?

KW

Comment by Reed O'Brien [ 29/Sep/11 ]

Krzysztof, you can grab the old 1.8.x mongodump binary from the distribution on the downloads page and use that in place of the broken one. It works fine with 2.0.

Jira says the 2.0.1 release is due today, FWIW.

Cheers,
~ro

Comment by Krzysztof Wilczynski [ 29/Sep/11 ]

I was wondering, when do you guys scheduled 2.0.1 release? This is stopping me from taking backups in a sensible way in my infrastructure – and probably not only me

Comment by Krzysztof Wilczynski [ 23/Sep/11 ]

Excellent! Thank you again I will wait for new package to surface

Comment by Spencer Brody (Inactive) [ 23/Sep/11 ]

This will be included in the 2.0.1 patch release.

Comment by auto [ 23/Sep/11 ]

Author:

{u'login': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@10gen.com'}

Message: Use slaveOk read in mongodump to allow dumping of secondaries. SERVER-3854.
Branch: v2.0
https://github.com/mongodb/mongo/commit/99b2d74eb9e8f45fdb2b6da7e57e5faecf9b5ef3

Comment by Krzysztof Wilczynski [ 23/Sep/11 ]

Thanks for this! Spencer +1

Will this be included in 2.1 release, or there will be a 2.0.1 version?

KW

Comment by auto [ 23/Sep/11 ]

Author:

{u'login': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@10gen.com'}

Message: Use slaveOk read in mongodump to allow dumping of secondaries. SERVER-3854.
Branch: master
https://github.com/mongodb/mongo/commit/6249553faa8da3468397309a68e1abc45f1d0a72

Comment by Spencer Brody (Inactive) [ 22/Sep/11 ]

This issue has been reproduced. Looking into root cause and fix.

Comment by Krzysztof Wilczynski [ 21/Sep/11 ]

I have the exact same problem, and can provide logs etc when needed; or a tar-ball of an LXC container running instance of Mongo 2.0, if needed

KW

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