Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-42555

gomemcached does not mark as fatal OS and timeout errors

    XMLWordPrintable

    Details

    • Triage:
      Untriaged
    • Story Points:
      1
    • Is this a Regression?:
      Unknown

      Description

      Marking it as query, but it affects any component that uses go-couchbase or gomemcached.
      When a gomemcached Get() ends prematurely (the most likely cause being a golang timeout),
      client/transport.go:getResponse() leaves the response structure uninitialized, which means that it has a 0 status.
      This is not picked as fatal, and the connection gets eventually reused, reading incorrectly, data left behind on the wire.

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

          There are no commits yet on this issue.

            People

            Assignee:
            mihir.kamdar Mihir Kamdar
            Reporter:
            marco.greco Marco Greco
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Gerrit Reviews

                There are no open Gerrit changes

                  PagerDuty