[SERVER-18206] renameCollection should handle WriteConflictException Created: 25/Apr/15  Updated: 23/Apr/19  Resolved: 23/Apr/19

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

Type: Bug Priority: Minor - P4
Reporter: Geert Bosch Assignee: Geert Bosch
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-31022 renameCollection with dropTarget can ... Closed
Operating System: ALL
Sprint: Quint Iteration 3, Quint Iteration 4, Quint Iteration 5, Storage NYC 2019-05-06
Participants:

 Description   

Like SERVER-17061, this command should be robust to WriteConflictException. Unlike the commands in SERVER-17061, these commands depend at least on SERVER-17062, which makes query execution robust to WriteConflictException.

This ticket as split off of SERVER-17075, as the renameCollection is more involved and quite separate from cloneCollectionAsCapped.



 Comments   
Comment by Eric Milkie [ 12/Apr/19 ]

geert.bosch I think this one is already fixed now?

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