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

Delay response to set operations when approaching Temp OOM

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: 1.7.0
    • Fix Version/s: None
    • Component/s: couchbase-bucket
    • Security Level: Public
    • Labels:
      None

      Description

      When we are approaching Temp OOM it would be beneficial to users if the response time of the set requests would be delayed when approaching a Temp OOM state. This would allow users to use client libraries that didn't support exponential backoff and function well when approaching a Temp OOM state.

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

        Activity

        Hide
        dustin Dustin Sallings (Inactive) added a comment -

        There's general concern about pushing things that respond to scalability problems to the centralized point where the scalability problem is. Slowing things down means that we either have to stop connection threads (in-line sleep) or suspend and re-awaken connections (requiring lots of timers firing and stuff).

        Show
        dustin Dustin Sallings (Inactive) added a comment - There's general concern about pushing things that respond to scalability problems to the centralized point where the scalability problem is. Slowing things down means that we either have to stop connection threads (in-line sleep) or suspend and re-awaken connections (requiring lots of timers firing and stuff).
        Hide
        trond Trond Norbye added a comment -

        THis shouldn't be done on the server (at least not in ep-engine) since it'll affect everyone going through moxi (since moxi is reusing a set of connections). If we want to be nice to "dumb" clients this should be done inside moxi (but I really think the logic belongs in the client)

        Show
        trond Trond Norbye added a comment - THis shouldn't be done on the server (at least not in ep-engine) since it'll affect everyone going through moxi (since moxi is reusing a set of connections). If we want to be nice to "dumb" clients this should be done inside moxi (but I really think the logic belongs in the client)

          People

          • Assignee:
            dustin Dustin Sallings (Inactive)
            Reporter:
            mikew Mike Wiederhold
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes