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

indexer.numSliceWriters=runtime.NumCPU() policy doesn't work very well when there are many Plasma instances

    XMLWordPrintable

Details

    Description

      Build 5.5.0-2414.

      Mapping the number of writer threads to the number of CPU cores is not always a good idea. I attempted to create ten partitioned indexes on my 48-core server and the indexer process was OOM-killed almost immediately.

      Although it's possible to mitigate this issue by tuning indexer.numSliceWriters option, a global thread pool with fair scheduling seems more appropriate.

      MB-29009 describes the environment and secondary indexes.

      Attachments

        1. indexer_5.5.0-2785_c1.svg
          236 kB
        2. indexer_5.5.0-2785_c2.svg
          218 kB
        3. indexer_5.5.0-2785_c3.svg
          225 kB
        4. indexer_5.5.0-2785_c4.svg
          216 kB
        5. indexer_5.5.0-2785-non_part.svg
          244 kB
        6. indexer_rss.png
          indexer_rss.png
          29 kB

        Issue Links

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

          Activity

            People

              sarath Sarath Lakshman
              pavelpaulau Pavel Paulau (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty