[SERVER-84201] Update findAndModify_upsert.js to skip checks when staleConfig is thrown Created: 14/Dec/23 Updated: 15/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kruti Shah | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Cluster Scalability
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 5 | ||||
| Description |
|
When findAndModify throws staleConfig, it will not return a value field in the response with the document that the concurrency test expects to be present to confirm that a doc was upsertedĀ here. Change this logic to only check the upserted document value when res.value is defined and not null. |