[SERVER-25204] CSRS config servers require majority write concern even for local database in 3.3.10 Created: 21/Jul/16  Updated: 13/Aug/16  Resolved: 25/Jul/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.3.11

Type: Bug Priority: Major - P3
Reporter: Louisa Berger Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-20945 CSRS config servers require majority ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 18 (08/05/16)
Participants:

 Description   

CSRS config servers require majority write concern even for local database in 3.3.10.

2016-07-21T16:30:11.432-0400 I CONTROL  [initandlisten] ** NOTE: This is a development version (3.3.10) of MongoDB.
csrs_set:PRIMARY> use local
switched to db local
csrs_set:PRIMARY> db.x.insert({"x" : 1}, {writeConcern:{w:1}})
WriteResult({
    "writeError" : {
        "code" : 2,
        "errmsg" : "w:'majority' is the only valid write concern when writing to config servers, got: { w: 1, wtimeout: 0 }"
    }
})

This was changed for the local db in 3.2 (SERVER-20945), but it's back in 3.3.10. Can we make the exception again for the local database in 3.4?



 Comments   
Comment by Kaloian Manassiev [ 29/Jul/16 ]

This change is checked-in so you should be able to get any of the nightly Evergreen builds.

Comment by Louisa Berger [ 29/Jul/16 ]

Nevermind, just got Mike to build it instead. Thanks!

Comment by Louisa Berger [ 29/Jul/16 ]

kaloian.manassiev – we need the Enterprise Amazon Linux build, not the Enterprise RHEL 6.2 build. Is there a quick way to get that build instead?

Thanks!

Comment by Githook User [ 25/Jul/16 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-25204 Allow writeConcern w:1 for 'local' on CSRS config servers
Branch: master
https://github.com/mongodb/mongo/commit/8855c03bdf307ef74825e0274344b1ce8df0852b

Comment by Daniel Pasette (Inactive) [ 24/Jul/16 ]

Looks like this was changed back here:

commit 7c67f3a6fd52ea4933c23ce89f1cc5da62628ec4
Author: Kaloian Manassiev <kaloian.manassiev@mongodb.com>
Date:   Thu Jun 30 14:32:38 2016 -0400
 
    SERVER-24858 Tighten assertions around waiting for write concern

This is a blocker for automation 3.4 upgrade development work.

Comment by Louisa Berger [ 21/Jul/16 ]

We write to the local database on all CSRS members so that other processes know when they can perform rolling updates.

Comment by Kaloian Manassiev [ 21/Jul/16 ]

Can you please explain what is the scenario where you need to do writes to the local database on the CSRS primary?

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