[SERVER-78496] Clear shard filtering metadata before releasing the critical section in rename participants Created: 28/Jun/23 Updated: 29/Oct/23 Resolved: 13/Jul/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 6.0.7, 7.0.0-rc5 |
| Fix Version/s: | 7.1.0-rc0, 7.0.0-rc8, 6.0.10 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Sergi Mateo Bellido |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v7.0, v6.0
|
||||
| Sprint: | Sharding EMEA 2023-07-10, Sharding EMEA 2023-07-24 | ||||
| Participants: | |||||
| Description |
|
In v5.0 there was a routing table refresh+wait for flush right before releasing the critical section in rename participants. That code snippet (or something similar) should be reintroduced because it is a way to ensure that both primary and secondaries will update their filtering info for source and target namespaces, properly reacting when a stale router tries to target them. Instead of simply refreshing, a better way would be to force a metadata refresh + setting the new filtering metadata as currently done by the collmod participant. |
| Comments |
| Comment by Githook User [ 30/Aug/23 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: (cherry picked from commit 016e42ba39231e035593032810021f974fb8f877) |
| Comment by Githook User [ 13/Jul/23 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: (cherry picked from commit 016e42ba39231e035593032810021f974fb8f877) |
| Comment by Githook User [ 11/Jul/23 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |