[SERVER-26168] repairDatabaseAndCheckVersion uses AutoGetCollectionForRead Created: 19/Sep/16 Updated: 19/Nov/16 Resolved: 20/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 3.3.12 |
| Fix Version/s: | 3.3.14 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding 2016-10-10 |
| Participants: |
| Description |
|
The repairDatabaseAndCheckVersion call, which runs at server startup is using AutoGetCollectionForRead, which performs sharding and replication snapshot checks. Doing this when the server is starting, while possibly not harmful is not correct. AutoGetCollection should be sufficient to use given that the global lock is already held in MODE_X. |
| Comments |
| Comment by Githook User [ 20/Sep/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |