[SERVER-16262] WriteConflict during concurrent map-reduce operations in WT Created: 21/Nov/14  Updated: 18/Dec/14  Resolved: 15/Dec/14

Status: Closed
Project: Core Server
Component/s: Concurrency, Storage
Affects Version/s: 2.8.0-rc0
Fix Version/s: 2.8.0-rc3

Type: Bug Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Geert Bosch
Resolution: Done Votes: 0
Labels: 28qa, wiredtiger
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

Happens when using the "reduce" action to combine the results of multiple threads into the same collection.

mr failed, removing collection :: caused by :: WriteConflict
Uncaught std::exception: std::exception, terminating



 Comments   
Comment by Githook User [ 16/Dec/14 ]

Author:

{u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}

Message: SERVER-16262: Add test case for Map/Reduce WriteConflict
Branch: master
https://github.com/mongodb/mongo/commit/35d89db03ecb922e3b43a1b1f8f0aaab3794d87f

Comment by Geert Bosch [ 15/Dec/14 ]

This was fixed as a side effect of SERVER-16429.

Comment by Geert Bosch [ 15/Dec/14 ]

This was fixed by: SERVER-16429 Add ScopedTransaction to AutoGetCollectionForRead and Map-reduce.

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