[SERVER-38326] mongos mapReduce cleanup doesn't obey request's writeConcern Created: 29/Nov/18  Updated: 29/Oct/23  Resolved: 02/May/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.1.5
Fix Version/s: 4.1.11

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Fixed Votes: 0
Labels: open_todo_in_code, todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-43476 Unblacklist mapReduce test in multi_t... Backlog
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2019-04-22, Sharding 2019-05-06
Participants:

 Description   

https://github.com/mongodb/mongo/blob/r4.1.5/src/mongo/s/commands/cluster_map_reduce_cmd.cpp#L731

Note: this might be a minor issue in the real world, but it causes some issue in transaction testing because of 2 phase drops. The drop can acquire the database X lock later after the mapReduce has already finished and conflict with the transactions trying to get the same lock in the tests.



 Comments   
Comment by Githook User [ 02/May/19 ]

Author:

{'name': 'Randolph Tan', 'username': 'renctan', 'email': 'randolph@10gen.com'}

Message: SERVER-38326 mongos mapReduce cleanup doesn't obey request's writeConcern
Branch: master
https://github.com/mongodb/mongo/commit/31559a02ae0f76698c26353cbd787b4744f72cd1

Comment by Randolph Tan [ 03/Dec/18 ]

kaloian.manassiev I temporarily blacklisted the map-reduce related tests in the passthrough because of this, the priority would depend on how bad we want to test mapReduce running before/after a multi-statment transaction.

Comment by Kaloian Manassiev [ 03/Dec/18 ]

renctan, is this something we need to do this iteration in order to unblock Cross-shard Transactions testing? It should be a fairly easy change and we can schedule it soon-ish.

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