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

[BP of MB-43886 to 6.6.5] - Usage of global cluster info client object

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Fix
    • Critical
    • 6.6.6
    • Cheshire-Cat
    • secondary-index
    • None
    • Untriaged
    • 1
    • Unknown

    Description

      Currently, indexer uses multiple cluster info client objects i.e. each component in indexer has a separate cluster info client object. When there is a pool/service change notification, all these clients would refresh their cache resulting in significant load at ns_server.

      Instead, indexer/projector process can maintain only on global cluster info client rather than initialising one per component. To do this, the updation of the cache data has to be made "Copy-On-Write".

      With out copy-on-write, it may not be possible to maintain a global cluster info cache as it would lead to significant RLock and WLock contention between different components.

      Attachments

        Issue Links

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

          Activity

            People

              sai.teja Sai Krishna Teja
              varun.velamuri Varun Velamuri
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty