[SERVER-44113] Refresh metadata for correct namespace in transactions_reject_writes_for_moved_chunks.js hashed case Created: 18/Oct/19 Updated: 29/Oct/23 Resolved: 21/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1, 4.2.2 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| 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 | ||||||||
| Backport Requested: |
v4.2
|
||||||||
| Sprint: | Sharding 2019-11-04 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 9 | ||||||||
| Description |
|
transactions_reject_writes_for_moved_chunks.js verifies that a transaction that targets a chunk that has been moved since a transaction began will fail for sharded collections with range and hashed keys. In some test cases, the targeted chunk is moved twice and a refresh if forced on the chunk's recipient to avoid a StaleConfig error when the transaction targets it. The refresh is currently always for the range based collection namespace (ns is defined here), so the shard is not guaranteed to be fresh in the hashed case. Instead, the hashed collection namespace should be refreshed in the hashed test cases. |
| Comments |
| Comment by Githook User [ 21/Oct/19 ] |
|
Author: {'name': 'Jack Mulrow', 'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com'}Message: (cherry picked from commit 713f6dd0dd90a000cb624c8d10ed2dfbdcd15772) |
| Comment by Githook User [ 21/Oct/19 ] |
|
Author: {'name': 'Jack Mulrow', 'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com'}Message: |