[SERVER-26860] add more unittests for compatible-first locking policy Created: 01/Nov/16 Updated: 24/Jul/17 Resolved: 18/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.13, 3.4.2, 3.5.1 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Geert Bosch | 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: | |||||
| Description |
|
When MongoDB switches to compatible-first locking policy, it needs to apply this policy to new incoming requests as well as currently pending ones. We should have unit tests that test the following scenarios:
|
| Comments |
| Comment by Githook User [ 02/Feb/17 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: (cherry picked from commit e36723dd520ca56ba9b0c59a711207741e422697) |
| Comment by Githook User [ 23/Jan/17 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: (cherry picked from commit e36723dd520ca56ba9b0c59a711207741e422697) |
| Comment by Githook User [ 18/Nov/16 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: |