[SERVER-1976] query failed : admin.$cmd { replSetStepDown: true } to: localhost:27018 Created: 20/Oct/10  Updated: 17/Mar/11  Resolved: 20/Oct/10

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

Type: Bug Priority: Trivial - P5
Reporter: David Mytton Assignee: Kristina Chodorow (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Tue Oct 19 22:19:33 db version v1.7.2-pre-, pdfile version 4.5
Tue Oct 19 22:19:33 git version: 2d4cf480d585df76dac2f1f0e669408a78be14c2
Tue Oct 19 22:19:33 sys info: Linux domU-12-31-39-06-79-A1 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


Operating System: ALL
Participants:

 Description   

1) Set up a 3 member replica set - master, secondary and arbiter

2) Step down the master so secondary becomes master

3) Step down the new master so they switch back

> rs.stepDown()
Sun Oct 17 23:03:41 query failed : admin.$cmd

{ replSetStepDown: true }

to: localhost:27018
Sun Oct 17 23:03:41 Error: error doing query: failed shell/collection.js:148



 Comments   
Comment by Kristina Chodorow (Inactive) [ 20/Oct/10 ]

As of 1.7.2, stepDown, reconfig, remove, etc (anything that could change who the primary is) will close all database connections, so you'll get an error in the shell. I added a note to the documentation: http://www.mongodb.org/display/DOCS/Replica+Set+Commands

Generated at Thu Feb 08 02:58:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.