[DOCS-12267] Docs for SERVER-38461: performSingleUpdateOpWithDupKeyRetry loops indefinitely Created: 13/Dec/18  Updated: 13/Nov/23  Resolved: 23/Jan/20

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.1.7, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Jeffrey Allen
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-38461 performSingleUpdateOpWithDupKeyRetry ... Closed
Participants:
Days since reply: 4 years, 2 weeks, 6 days ago
Epic Link: DOCS: 4.2 Server/Tools

 Description   

Description

Description:

Documentation changes are only needed if we discuss the scenario where 2 upserts can both attempt to insert, with one failing on DuplicateKey. With this ticket there are now scenarios where we will try the failed upsert and it can succeed.

Engineering Ticket Description:

UpdateStage::shouldRetryDuplicateKeyException should not return true for the replacement style upserts. See the repro.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by James Wahlin [ 23/Jan/20 ]

No objection from me. Thanks!

Comment by Jeffrey Allen [ 23/Jan/20 ]

Ah got it james.wahlin, thanks for the links to those tickets. If there are no objections I'll close this ticket then since it doesn't seem like we cover the specific scenario that the linked SERVER ticket addresses.

Comment by James Wahlin [ 23/Jan/20 ]

jeffrey.allen - I would leave the second line in place. The work we did under SERVER-37124 does allow us to retry and update in some scenarios, but there will still be cases where we have to fail. See the summary in SERVER-14322 for details on potential scenarios and which we can retry.

Comment by Githook User [ 03/Jul/19 ]

Oops – the following was for DOCS-12667 (sigh)

Author:

{'name': 'Kay Kim', 'username': 'kay-kim', 'email': 'kay.kim@10gen.com'}

Message: DOCS-12267: 4.2 rs.status optime walltimes
Branch: master
https://github.com/mongodb/docs/commit/3bbb19634beb0b5228253a8058084ba4a03cc902

Generated at Thu Feb 08 08:04:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.