[SERVER-71966] Investigate InternalOnly leaks Created: 08/Dec/22  Updated: 12/Dec/23

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

Type: Bug Priority: Major - P3
Reporter: Alex Li Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: cs-subteam1, sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-49040 Avoid transmission of internal-only e... Closed
Assigned Teams:
Cluster Scalability
Operating System: ALL
Participants:
Story Points: 4

 Description   

As part of SERVER-49040, for network responses, there is a tassert checking all error codes for InternalOnly. The check is skipped when the target is internal.

There are 3 error codes that cause test failures due to this check, so InternalOnly was removed from these error codes:

TransactionCoordinatorSteppingDown

TransactionCoordinatorReachedAbortDecision

CollectionIsEmptyLocally

 

Here is a patch where InternalOnly is removed from CollectionIsEmptyLocally: spruce link. (look at jstests/sharding/analyze_shard_key/analyze_shard_key_basic.js)

Here is a patch where InternalOnly is removed from the TransactionCoordinator error codes: spruce link. (look at jstests/concurrency/fsm_workloads/multi_statement_transaction_simple_repeated_reads.js and jstests/sharding/cancel_coordinate_txn_commit_with_tickets_exhausted.js

 


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