[SERVER-23807] Updates should always throw WriteConflictException on unindexing Created: 19/Apr/16 Updated: 02/Aug/18 Resolved: 21/Apr/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, WiredTiger |
| Affects Version/s: | 3.2.5, 3.3.4 |
| Fix Version/s: | 3.0.12, 3.2.6, 3.3.5 |
| Type: | Task | Priority: | Critical - P2 |
| Reporter: | Kyle Suarez | Assignee: | Kyle Suarez |
| Resolution: | Done | Votes: | 1 |
| Labels: | code-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Backport Completed: | |||||||||||||||||
| Sprint: | Integration 13 (04/22/16) | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
During an index build, the collection is locked in mode IX. Consider a background index build occurring with concurrent updates. Then, the following race scenario could occur: 1. Both the updater and the index builder read the same document. We can fix this by having the update path trigger a write conflict exception even in the "no-op" case when unindexing returns WT_NOTFOUND. (An alternative is to simply lock the collection in X mode during an index build, but this will probably have a large impact on performance.) |
| Comments |
| Comment by Githook User [ 29/Apr/16 ] |
|
Author: {u'username': u'ksuarz', u'name': u'Kyle Suarez', u'email': u'ksuarz@gmail.com'}Message: Index builds must lock the collection with an X lock, rather than an IX lock, to |
| Comment by Githook User [ 21/Apr/16 ] |
|
Author: {u'username': u'ksuarz', u'name': u'Kyle Suarez', u'email': u'ksuarz@gmail.com'}Message: There are two distinct fixes that must be done together:
|
| Comment by Githook User [ 21/Apr/16 ] |
|
Author: {u'username': u'ksuarz', u'name': u'Kyle Suarez', u'email': u'ksuarz@gmail.com'}Message: There are two distinct fixes that must be done together:
|