[SERVER-19875] Switch to using the LockManager to guard access to the current CatalogManager Created: 11/Aug/15 Updated: 06/Dec/22 Resolved: 14/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | csrsupgrade | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Sharding F (01/29/16) | ||||||||||||
| Participants: | |||||||||||||
| Comments |
| Comment by Spencer Brody (Inactive) [ 14/Jan/16 ] |
|
3.2 was released without this and we haven't noticed any performance problems from the sharded mutex currently used to guard the catalog manager. We can revisit this if perf problems arise in the future. |
| Comment by Githook User [ 25/Aug/15 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Githook User [ 25/Aug/15 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Githook User [ 25/Aug/15 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Githook User [ 25/Aug/15 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |