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

Expose GSI cache stats on UI

    XMLWordPrintable

Details

    Description

      For Standard GSI, it would be good to expose cache stats on the UI(resident ratio, cache hit/miss, disk fetches etc).

      Source - Forum user (https://forums.couchbase.com/t/measure-caching-of-gsis/13778)

      Attachments

        Issue Links

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

          Activity

            Sarath Lakshman any update on this?

            ajit.yagaty Ajit Yagaty [X] (Inactive) added a comment - Sarath Lakshman any update on this?

            cache_hit_percent consists of both read and write hits because of read/write caches are shared.

            sarath Sarath Lakshman added a comment - cache_hit_percent consists of both read and write hits because of read/write caches are shared.

            Build couchbase-server-5.5.0-1955 contains ns_server commit c15ef456cc6fc1b08250251882abdde869a1a4ad with commit message:
            MB-25670: Expose GSI cache stats in UI.
            https://github.com/couchbase/ns_server/commit/c15ef456cc6fc1b08250251882abdde869a1a4ad

            build-team Couchbase Build Team added a comment - Build couchbase-server-5.5.0-1955 contains ns_server commit c15ef456cc6fc1b08250251882abdde869a1a4ad with commit message: MB-25670 : Expose GSI cache stats in UI. https://github.com/couchbase/ns_server/commit/c15ef456cc6fc1b08250251882abdde869a1a4ad
            perry Perry Krug added a comment -

            Out of curiosity, does this now give us a single REST endpoint that will expose indexer stats across the whole cluster (like pools/default/buckets/stats) or would one still need to query each indexer separately?

            perry Perry Krug added a comment - Out of curiosity, does this now give us a single REST endpoint that will expose indexer stats across the whole cluster (like pools/default/buckets/stats) or would one still need to query each indexer separately?

            Hi Perry, no this MB is for exposing the above stats in the UI only. One would still need to query each indexer separately for these stats and ns_server doesn't have an explicit endpoint to expose indexer stats across the cluster.

            ajit.yagaty Ajit Yagaty [X] (Inactive) added a comment - Hi Perry, no this MB is for exposing the above stats in the UI only. One would still need to query each indexer separately for these stats and ns_server doesn't have an explicit endpoint to expose indexer stats across the cluster.

            People

              ajit.yagaty Ajit Yagaty [X] (Inactive)
              deepkaran.salooja Deepkaran Salooja
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty