[SERVER-24563] Secondary crash when inserting document into db with different case Created: 14/Jun/16 Updated: 05/Apr/17 Resolved: 18/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Write Ops |
| Affects Version/s: | 3.3.8 |
| Fix Version/s: | 3.2.12, 3.4.2, 3.5.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Isabella Siu (Inactive) | Assignee: | Geert Bosch |
| Resolution: | Done | Votes: | 0 |
| Labels: | bkp | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Backport Requested: |
v3.4, v3.2
|
||||||||||||||||||||||||
| Sprint: | Storage 2016-11-21, Storage 2016-12-12 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||||||
| Description |
|
When different threads are inserting into databases with the same name in different cases the secondary crashes
|
| Comments |
| Comment by Githook User [ 13/Jan/17 ] |
|
Author: {u'username': u'dgottlieb', u'name': u'Daniel Gottlieb', u'email': u'daniel.gottlieb@10gen.com'}Message: |
| Comment by Githook User [ 13/Jan/17 ] |
|
Author: {u'username': u'dgottlieb', u'name': u'Daniel Gottlieb', u'email': u'daniel.gottlieb@10gen.com'}Message: (cherry picked from commit dceaf6bf28fb879eb23f3c022647ee3e8f15c370) Modifications for backport: |
| Comment by Githook User [ 11/Jan/17 ] |
|
Author: {u'username': u'dgottlieb', u'name': u'Daniel Gottlieb', u'email': u'daniel.gottlieb@10gen.com'}Message: Revert " This reverts commit d75f8c7cf92fcf4c6089e27ff548d0ed1fccb1a0. |
| Comment by Githook User [ 11/Jan/17 ] |
|
Author: {u'username': u'dgottlieb', u'name': u'Daniel Gottlieb', u'email': u'daniel.gottlieb@10gen.com'}Message: (cherry picked from commit dceaf6bf28fb879eb23f3c022647ee3e8f15c370) Modifications for backport: |
| Comment by Githook User [ 11/Jan/17 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'redbeard0531@gmail.com'}Message: Revert " This reverts commit e262daabeabaa00885c2aaecf22ace0255724008. |
| Comment by Githook User [ 11/Jan/17 ] |
|
Author: {u'username': u'dgottlieb', u'name': u'Daniel Gottlieb', u'email': u'daniel.gottlieb@10gen.com'}Message: (cherry picked from commit dceaf6bf28fb879eb23f3c022647ee3e8f15c370) Modifications for backport: |
| Comment by Githook User [ 09/Jan/17 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: |
| Comment by Githook User [ 18/Nov/16 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: |
| Comment by Eric Milkie [ 26/Oct/16 ] |
|
I believe this means you could successfully create two databases that only differ by case, and insert data into both. But new clients would have trouble accessing either one – in addition to the crash you would experience on secondaries of a replica set. |
| Comment by Eric Milkie [ 26/Oct/16 ] |
|
There is a race when checking for duplicate database names that only vary by case. We don't hold the lock between checking for a duplicate and adding the new database to the list. |