[SERVER-79609] Fix `findAndModify_upsert.js` test to accept StaleConfig error Created: 02/Aug/23 Updated: 29/Oct/23 Resolved: 08/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0, 7.0.1, 6.0.10, 5.0.21 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pau Baldillou Salse (Inactive) | Assignee: | Pau Baldillou Salse (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v7.0, v6.0, v5.0
|
||||||||||||
| Sprint: | Sharding EMEA 2023-08-21 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 25 | ||||||||||||
| Description |
|
It can happen that due to the majority write need when getting metadata from CSRS, if replication is off due to a stepdown, findAndModify gets a StaleConfig error. This behaviour makes sense, so the test should be fixed. |
| Comments |
| Comment by Githook User [ 21/Aug/23 ] |
|
Author: {'name': 'Pau Baldillou Salse', 'email': 'pau.baldillou-salse@mongodb.com', 'username': ''}Message: |
| Comment by Githook User [ 09/Aug/23 ] |
|
Author: {'name': 'Pau Baldillou Salse', 'email': 'pau.baldillou-salse@mongodb.com', 'username': ''}Message: |
| Comment by Githook User [ 09/Aug/23 ] |
|
Author: {'name': 'Pau Baldillou Salse', 'email': 'pau.baldillou-salse@mongodb.com', 'username': ''}Message: |
| Comment by Githook User [ 08/Aug/23 ] |
|
Author: {'name': 'Pau Baldillou Salse', 'email': '69910092+pbaldisa@users.noreply.github.com', 'username': 'pbaldisa'}Message: |