[SERVER-50218] Change shard server and config server op observers to handle $v:2 delta updates Created: 10/Aug/20 Updated: 29/Oct/23 Resolved: 10/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ian Boros | Assignee: | Ian Boros |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Query 2020-08-24, Query 2020-09-07, Query 2020-09-21 |
| Participants: |
| Description |
|
The shard server op observer parses updates to config.cache.collections and config.rangeDeletions to maintain in-memory state about the routing table. See here. This code will need to be changed to handle both the $v:1 update format and $v:2 update format. The config server op observer appears to have logic which will need similar changes. |
| Comments |
| Comment by Githook User [ 09/Sep/20 ] |
|
Author: {'name': 'Ian Boros', 'email': 'ian.boros@mongodb.com', 'username': 'puppyofkosh'}Message: |
| Comment by Ian Boros [ 10/Aug/20 ] |
|
We should make sure someone on sharding has a chance to review this. |