[SERVER-23491] set_majority_read_and_write_concerns.js doesn't work for updates Created: 04/Apr/16 Updated: 18/Nov/16 Resolved: 26/Apr/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.7, 3.3.6 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Michael Grundy |
| Resolution: | Done | Votes: | 0 |
| Labels: | test-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Completed: | |||||||||||||||||
| Sprint: | TIG 13 (04/22/16), TIG 14 (05/13/16) | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||
| Description |
|
The overrides aren't replacing the writeConcern for updates. Initial testing showed this to an issue for updates which supply a writeConcern, so some code paths might add a writeConcern correctly. |
| Comments |
| Comment by Githook User [ 10/May/16 ] | ||||||||||||||||||||
|
Author: {u'username': u'mgrundy', u'name': u'Mike Grundy', u'email': u'michael.grundy@10gen.com'}Message: (cherry picked from commit 19d3e69975d32bf8f358aafe4067d578a4bf4440) Conflicts: | ||||||||||||||||||||
| Comment by Githook User [ 26/Apr/16 ] | ||||||||||||||||||||
|
Author: {u'username': u'mgrundy', u'name': u'Mike Grundy', u'email': u'michael.grundy@10gen.com'}Message: | ||||||||||||||||||||
| Comment by Githook User [ 06/Apr/16 ] | ||||||||||||||||||||
|
Author: {u'username': u'IanWhalen', u'name': u'Ian Whalen', u'email': u'ian.whalen@gmail.com'}Message: | ||||||||||||||||||||
| Comment by Michael Grundy [ 05/Apr/16 ] | ||||||||||||||||||||
|
ian.whalen Either disable update_multi5.js or revert the change that added the w:1 writeConcern to the update. We're going to change where we override the writeConcern so it's more resilient. Right now if there is no writeConcern passed in then the bulk api will call getWriteConcern (which we have overridden). | ||||||||||||||||||||
| Comment by Ian Whalen (Inactive) [ 04/Apr/16 ] | ||||||||||||||||||||
|
michael.grundy should we start this by disabling update_multi5.js in this suite until you've got a real fix? | ||||||||||||||||||||
| Comment by Scott Hernandez (Inactive) [ 04/Apr/16 ] | ||||||||||||||||||||
|
Example, with logging in the override function to print "processing <cmd>" for all processed commands:
|