Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-43056

Allow specification of errorLabels in failCommand

    • Type: Icon: New Feature New Feature
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Service Arch

      It would be helpful for driver testing if errorLabels could be specified as part of a failCommand failpoint. Alternatively, the errorLabels could simply populated according to the error code's category as they are for real errors.

      Also, I'm required to set an assignee for this, but wasn't exactly sure where to send it. I apologize in advance if the platform team backlog is not the correct place.

      Edit: upon further inspection, I've found that the alternative mentioned above is how failCommand currently works. i.e. The server is setting errorLabels according to the category (e.g. 280 and NonResumableChangeStreamError). That makes this work lower priority, but it would probably still be useful if drivers could trigger errors with specific labels in their tests.

            Assignee:
            backlog-server-servicearch [DO NOT USE] Backlog - Service Architecture
            Reporter:
            patrick.freed@mongodb.com Patrick Freed
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: