Uploaded image for project: 'Go Driver'
  1. Go Driver
  2. GODRIVER-1920

Aggregate can time out without setting socket options

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor - P4 Minor - P4
    • None
    • None
    • None
    • None
    • Not Needed

    Description

      It seems that aggregate can occasionally cause a timeout with a tcp error like
      unable to decode message length: read tcp 10.1.129.128:65170->3.216.165.122:27017: read: operation timed out
      even when no options related to timeouts have been set.

      This operation should not timeout, as the default socket options are supposed to block indefinitely. Some timeout, either default or manually-set, is causing this failure.

      Attachments

        Activity

          People

            Unassigned Unassigned
            benji.rewis@mongodb.com Benji Rewis (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: