Uploaded image for project: 'Data Foundation Bugs'
  1. Data Foundation Bugs
  2. DFBUGS-639

[2261881] Documentation need to be corrected for MDSCacheUsageHigh alert.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • odf-4.18
    • odf-4.15
    • ocs-operator
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • ?
    • Hide
      Cause: Ceph returns `ceph_mds_mem_rss` metric in Kilobytes (KB)

      Consequence: When the user is searching for the metric in OCS UI, the graphs shows the y axis in MB. This can cause confusion when the user is comparing the results for `MDSCacheUsageHigh` alert.

      Workaround (if any): Use `ceph_mds_mem_rss * 1000` when searching for this metric in the Openshift UI to see the graph y axis in GB.

      Result: Using `ceph_mds_mem_rss * 1000` will show the graph in GB, and user can easily compare the results shown in `MDSCacheUsageHigh` alert.
      Show
      Cause: Ceph returns `ceph_mds_mem_rss` metric in Kilobytes (KB) Consequence: When the user is searching for the metric in OCS UI, the graphs shows the y axis in MB. This can cause confusion when the user is comparing the results for `MDSCacheUsageHigh` alert. Workaround (if any): Use `ceph_mds_mem_rss * 1000` when searching for this metric in the Openshift UI to see the graph y axis in GB. Result: Using `ceph_mds_mem_rss * 1000` will show the graph in GB, and user can easily compare the results shown in `MDSCacheUsageHigh` alert.
    • Known Issue
    • None

      Description of problem (please be detailed as possible and provide log
      snippests):

      The document which has been provided as part of BZ-2256725 need corrections. This main use case of this doc is for adding memory to the MDS pod whenever the alert MDSCacheUsageHigh seen.

      Link to the doc:
      https://github.com/openshift/runbooks/blob/master/alerts/openshift-container-storage-operator/CephMdsCacheUsageHigh.md

      Version of all relevant components (if applicable):

      Does this issue impact your ability to continue to work with the product
      (please explain in detail what is the user impact)?

      Is there any workaround available to the best of your knowledge?

      Rate from 1 - 5 the complexity of the scenario you performed that caused this
      bug (1 - very simple, 5 - very complex)?

      1
      Can this issue reproducible?
      1

      Can this issue reproduce from the UI?

      If this is a regression, please provide more details to justify this:

      Steps to Reproduce:
      1.Maintain the MDS CPU load to reach 95% of the cache limit.

      2. MDSCacheHighUsage alert will be triggered in the dashboard.

      3. Go to the alert and click on the document linked to the alert.

      4. The document need to be more clear in sections "Impact" & "Mitigation".

      Actual results:
      Document has the steps to apply default memory in MDS pod

      Expected results:
      Document should have steps to Increase MDS pod memory from default to recommended based on the alert.

      Please refer attachment for more information.

      Additional info:

              sapillai Santosh Pillai
              rhn-support-nagreddy Nagendra Reddy
              Nagendra Reddy
              Nagendra Reddy Nagendra Reddy
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: