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

Allow users to specify reader and writer threads in the UI

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • 6.5.0
    • 6.5.0
    • UI
    • Untriaged
    • Unknown

    Description

      Seie MB-36923 for more details.

      We should allow users to specify reader and writer thread counts in the UI.

      The REST APIs to user are:
      GET: pools/default/settings/memcached/global
      POST: pools/default/settings/memcached/global 'num_reader_threads=8&num_writer_threads=8'

      See this patchset: http://review.couchbase.org/#/c/118320/

      We should add an "Advanced Data Service Settings" expando panel on the settings page. It should be below the rebalance settings and above the query settings.

      Valid settings for the reader and writer thread values are [0,64]. If 0 it means "use the normal defaults for the box on which Couchbase Server is deployed" - it depends on the number of cores.

      Ideally, when set to zero we would show some indication that this is the OOTB default setting. Perhaps we show something like:

      Number of reader threads: 0 (use server default value)
      Number of writer threads: 0 (use server default value)
      

      Please also include the following text next to the boxes.

      Setting higher values for reader and writer threads reduces latency in persisting items to and reading items from disk and increases throughput for synchronous write operations. It can result in greater write amplification and server CPU utilization. Consult Couchbase documentation and use care in setting these values.

      Attachments

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

        Activity

          I think the intent is to be able to customize reader and writer threads independently. e.g. I can choose to leave writer threads alone (at default settings) but customize reader threads only (either to disk i/o optimized or to a custom value).

          I don't think the proposed UI allows for that.

          shivani.gupta Shivani Gupta added a comment - I think the intent is to be able to customize reader and writer threads independently. e.g. I can choose to leave writer threads alone (at default settings) but customize reader threads only (either to disk i/o optimized or to a custom value). I don't think the proposed UI allows for that.

          Was this mistakenly moved to Cheshire Cat?

          shivani.gupta Shivani Gupta added a comment - Was this mistakenly moved to Cheshire Cat?

          Build couchbase-server-6.5.0-4920 contains ns_server commit e2e9dc6 with commit message:
          MB-37021: added reader and writer threads in the UI

          build-team Couchbase Build Team added a comment - Build couchbase-server-6.5.0-4920 contains ns_server commit e2e9dc6 with commit message: MB-37021 : added reader and writer threads in the UI
          ajay.bhullar Ajay Bhullar added a comment -

          verified in 6.5.0-4920, it works as described by rob in an earlier comment

          ajay.bhullar Ajay Bhullar added a comment - verified in 6.5.0-4920, it works as described by rob in an earlier comment

          Build couchbase-server-7.0.0-1135 contains ns_server commit e2e9dc6 with commit message:
          MB-37021: added reader and writer threads in the UI

          build-team Couchbase Build Team added a comment - Build couchbase-server-7.0.0-1135 contains ns_server commit e2e9dc6 with commit message: MB-37021 : added reader and writer threads in the UI

          People

            ajay.bhullar Ajay Bhullar
            dfinlay Dave Finlay
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty