[SERVER-80317] DuplicateKey error message is logged from findAndModify after 5.0 upgrade Created: 22/Aug/23  Updated: 30/Jan/24

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Ian Boros Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 0
Labels: query-product-scope-1, query-product-urgency-2, query-product-value-2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-74551 WriteConflictException unnecessarily ... Closed
Assigned Teams:
Query Execution
Operating System: ALL
Participants:

 Description   

In SERVER-43821, PlanExecutor was refactored so that certain errors which previously were not logged became logged.

One such error was WriteConflictException, which was problematic because it lead to spammy log messages. This was reported under SERVER-74551 and fixed by ensuring WriteConflictExceptions do not take the same logging path that other errors take.

Recently it came up that DuplicateKey error was not logged in 4.4.x but now is in 5.0. This results in extra warning log messages for users with certain workloads that tend to "expect" duplicate key errors from findAndModify. This ticket is to determine:

  • Is this a bug?
  • Is it something we should change? (Regardless of above)
  • If yes to above, are there other error types that we should also change?

Generated at Thu Feb 08 06:43:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.