[SERVER-50550] Add source connection metadata to translated connection-relevant error codes Created: 26/Aug/20  Updated: 06/Dec/22

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

Type: Improvement Priority: Major - P3
Reporter: Billy Donahue Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: sa-remove-fv-backlog-22
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-50549 Transform connection-related error co... Closed
Assigned Teams:
Service Arch
Participants:

 Description   

SERVER-50549 proposes new error codes for proxied commands to be returned in place of connection-relevant error codes in the proxy-forwarded command.

Certainly a client-driver needs to know that the connection experiencing an error is not the client-proxy connection. But it would be obviously nice to know which connection DID have the problem. So this ticket proposes an attachment of diagnostic metadata to the proxied connection error wrapper code (or codes), probably through ErrorExtraInfo mechanism. This metadata is not intended to be acted upon by client drivers.


Generated at Thu Feb 08 05:22:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.