[SERVER-21940] Workload connection cache in FSM suite is not nulled out properly Created: 18/Dec/15 Updated: 18/Nov/16 Resolved: 19/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 3.2.0 |
| Fix Version/s: | 3.2.3, 3.3.1 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Kamran K. | Assignee: | Jonathan Abrahams |
| Resolution: | Done | Votes: | 0 |
| Labels: | test-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Completed: | |||||||||
| Sprint: | TIG F (01/29/16) | ||||||||
| Participants: | |||||||||
| Description |
|
max.hirschhorn noticed that the code to null out the (currently unused) workload connection cache doesn't actually null out the connections: https://github.com/mongodb/mongo/blob/r3.2.0/jstests/concurrency/fsm_libs/fsm.js#L48-L54 You can repro the bug by applying this patch to master and then running the sharded concurrency suite:
Run the suite with this command: python buildscripts/resmoke.py --suites=concurrency_sharded |
| Comments |
| Comment by Githook User [ 19/Jan/16 ] |
|
Author: {u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}Message: (cherry picked from commit 39be026de1627f3d93d9cdd9528c17b16667402f) |
| Comment by Githook User [ 19/Jan/16 ] |
|
Author: {u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}Message: |