-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
ALL
-
4
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)
- is related to
-
SERVER-49040 Avoid transmission of internal-only errors
- Closed