Recovering from Network Failure

XMLWordPrintableJSON

    • Type: Question
    • Resolution: Gone away
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • Go Drivers
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      We are writing data to MongoDB Atlas using the Go Driver. We are seeing the following:
      ```
      log: 2026-04-28T05:07:39Z ERR exiting with error error="failed to sync v3 source <SOURCENAME>: rpc error: code = Internal desc = write failed: failed to flush: connection(<URI>.<URI>.mongo.com:1024[-23]) incomplete read of message header: connection closed unexpectedly by the other side: EOF: connection(<URI>.<URI>.mongo.com:1024[-23]) incomplete read of message header: connection closed unexpectedly by the other side: EOF" invocation_id=<UUID> module=cli
      ```

      A few questions:
      1. Is this safe to retry? How do we know when it is safe to retry?
      2. Can you add in user configurable Backoff and Retries to the Go Driver?

            Assignee:
            Matt Dale
            Reporter:
            Ben Bernays
            None
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: