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

Service pool idle time check must happen more often

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.0.10
    • None
    • None
    • 1

    Description

      Various couchbase server services have reduced their idle times
      to 5 seconds to help mitigate potential slowloris attacks. This
      unfortunately also has a profound impact on how quickly we need
      to clean up idle endpoints, otherwise the server terminates
      the sockets for us and we have noisy logs and lots of reconnect
      attempts.

      The default idle timeout has been reduced to 4.5s in a previous
      changeset, but when testing with recent 7.0 builds I noticed that
      connections were still terminated on us. Problem is, the actual
      timer that checks all endpoints on a periodical basis still had
      a much higher granularity (5s!). In empirical testing, moving
      it down to 500 millis looks to be granular enough to catch any
      idle endpoint and disconnect it before the chance gets a server
      to do so.

      Attachments

        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