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

Usage of global cluster info client object

    XMLWordPrintable

Details

    • Bug
    • Resolution: Resolved
    • Critical
    • 7.1.0
    • 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

          For Gerrit Dashboard: MB-43886
          # Subject Branch Project Status CR V

          Activity

            People

              hemant.rajput Hemant Rajput
              varun.velamuri Varun Velamuri
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There is 1 open Gerrit change

                  PagerDuty