Update replica config to max priority of 100.0

[msaffitz]

From 2.2

{
    "errmsg" : "exception: bad config for member[1] priorities must be between 0.0 and 100.0",
    "code" : 13135,
    "ok" : 0
}

[tychoish]

Hey,

Thanks so much for this catch! I'd really like to merge this change, but before I can, could you fill out the MongoDB/10gen contributor agreement? It's located here:

http://www.10gen.com/contributor

Thanks! And sorry about the delay in getting back to you.

Cheers,
sam

[msaffitz]

Sorry for the delay-- I've signed the agreement.

-- Mike

---

@msaffitz :: Follow me on Twitter at http://bit.ly/pTGkDW

On Oct 11, 2012, at 1:45 PM, Sam Kleinman [email protected] wrote:

Hey,

Thanks so much for this catch! I'd really like to merge this change, but before I can, could you fill out the MongoDB/10gen contributor agreement? It's located here:

http://www.10gen.com/contributor

Thanks! And sorry about the delay in getting back to you.

Cheers,
sam

—
Reply to this email directly or view it on GitHub.

[tychoish]

Sorry, for the delay on this on my part.

I've just looked at the code, and it looks like the message doesn't actually reflect the actual allowable values. I've issued the following issue/pull request to correct this, and I'll merge this change and update other docs as needed...

https://jira.mongodb.org/browse/SERVER-7380

Sorry about that. I'll update this request when I know more.

[tychoish]

Just to check back in on this, 2.3.1 (following the SERVER-7380 ticket) will remove this limitation, and I'll get the docs corrected early next week on this behavior. Sorry for taking so long on this, and thanks for unconvering this issue and helping making MongoDB better!

Cheers,
sam