[SERVER-2827] When priority is one, can't setting slaveDelay. Created: 24/Mar/11  Updated: 25/Mar/11  Resolved: 24/Mar/11

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

Type: Bug Priority: Major - P3
Reporter: Kunihiko Jikuya Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

linux x64


Operating System: ALL
Participants:

 Description   

I want to setting slaveDelay to node of priority one.

TEST PRIMARY> rs.reconfig(cfg);
{
"assertion" : "bad config for member[2] slaveDelay requires priority be zero",
"assertionCode" : 13135,
"errmsg" : "db assertion failure",
"ok" : 0
}



 Comments   
Comment by Eliot Horowitz (Inactive) [ 25/Mar/11 ]

I don't understand that question.
For general configuration questions, please use http://groups.google.com/group/mongodb-user/

Comment by Kunihiko Jikuya [ 25/Mar/11 ]

When setting slaveDelay node became PRIMARY, the configuration specification is disabled or not?

Comment by Eliot Horowitz (Inactive) [ 24/Mar/11 ]

Correct, this is how its supposed to since a slave delayed node should never be master.

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