[SERVER-32202] Do not clear the cached sharding filtering information on replication state changes Created: 07/Dec/17 Updated: 30/Oct/23 Resolved: 12/Dec/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.6.0 |
| Fix Version/s: | 3.6.2, 3.7.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v3.6
|
||||
| Sprint: | Sharding 2017-12-18 | ||||
| Participants: | |||||
| Case: | (copied to CRM) | ||||
| Description |
|
Prior to version 3.6, the shard secondaries did not support filtering based on the active chunk metadata and were required to not have any filtering metadata cached. Because of this on every replication state change we were clearing it "just in case" - step up / step down. With support for filtering in 3.6 this is no longer necessary and it also has negative performance impact due to the need to fetch the full metadata, so we should get rid of it. |
| Comments |
| Comment by Githook User [ 28/Dec/17 ] |
|
Author: {'username': 'kaloianm', 'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev'}Message: (cherry picked from commit 915bcc9ee3a396c857370fa6379408cb15e87a3e) |
| Comment by Githook User [ 12/Dec/17 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: |