[SERVER-61214] Ensure having the latest known entry of the catalog cache when creating config.system.sessions Created: 03/Nov/21 Updated: 29/Oct/23 Resolved: 03/Dec/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0, 5.0.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v5.0
|
||||||||||||
| Sprint: | Sharding EMEA 2021-11-15, Sharding EMEA 2021-11-29, Sharding EMEA 2021-12-13 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 35 | ||||||||||||
| Description |
|
After creating and sharding the config.system.sessions collection, there is a refresh that might not notice the creation of the sharded collection. This happens because the catalog cache cannot be trusted in secondaries in the config server, specifically, if a config server secondary haven't replicated the write changes and tries to create the indexes then it will end up targeting the config server instead of the shards. We should ensure that the changes have been replicated, we could for example do a write after creating the collection and wait for that configOpTime, or, find a way to get the configOpTime gossiped by the create collection response. |
| Comments |
| Comment by Githook User [ 14/Dec/21 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Githook User [ 03/Dec/21 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |