Uploaded image for project: 'Java Couchbase JVM Core'
  1. Java Couchbase JVM Core
  2. JVMCBC-380

Disable pipelining for HTTP services

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.4.1, 1.3.7
    • None
    • None

    Description

      In forum posts as well as other tickets it has been discovered that the implicit pipelining netty/core-io uses doesn't work well with the go implementation of pipelining in http 1.1. In fact, it doesn't work at all and leads to all kinds of weird issues, especially prematurely aborted (n1ql) requests that return a status of "Closed' and 0 as the result count.

      As a result, we need to disable pipelining for HTTP based services, but for performance reasons keep it for binary ops.

      Attachments

        Issue Links

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

          Activity

            There are no comments yet on this issue.

            People

              daschl Michael Nitschinger
              daschl Michael Nitschinger
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty