[SERVER-13388] mongos batch upconvert from legacy writes uses default write concern Created: 27/Mar/14  Updated: 11/Jul/16  Resolved: 28/Mar/14

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 2.6.0-rc3

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Greg Studer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

... which isn't correct if there are replica set shards with getLastErrorDefaults set. Legacy writes should always upconvert to w:1 batches.



 Comments   
Comment by Githook User [ 27/Mar/14 ]

Author:

{u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-13388 explicitly use w:1 for upconverted writes from mongos
(cherry picked from commit 696fba3bc9607ec5885d072d68c609895b7f5831)
Branch: v2.6
https://github.com/mongodb/mongo/commit/e6f210813e1b32f25885e1ea9d96cf1c8f5b05f4

Comment by Githook User [ 27/Mar/14 ]

Author:

{u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-13388 explicitly use w:1 for upconverted writes from mongos
Branch: master
https://github.com/mongodb/mongo/commit/696fba3bc9607ec5885d072d68c609895b7f5831

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