[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: |
|
||||||||
| Assigned Teams: |
Cluster Scalability
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Story Points: | 4 | ||||||||
| Description |
|
As part of 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)
|