Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-34360

The must-gather took too long after upgrading to OpenShift 4.14

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • None
    • 4.14
    • oc
    • Moderate
    • No
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, the `oc adm must-gather` command took a long time to gather CPU related performance data in large clusters. With this release, the data is gathered in parallel instead of sequentially, which shortens the data collection time. (link:https://issues.redhat.com/browse/OCPBUGS-34360[*OCPBUGS-34360*])
      Show
      * Previously, the `oc adm must-gather` command took a long time to gather CPU related performance data in large clusters. With this release, the data is gathered in parallel instead of sequentially, which shortens the data collection time. (link: https://issues.redhat.com/browse/OCPBUGS-34360 [* OCPBUGS-34360 *])
    • Bug Fix
    • Done

      Description of problem:

          After upgrading to OpenShift 4.14, the must-gather took much longer than before.

      Version-Release number of selected component (if applicable):

          4.14

      How reproducible:

          Always

      Steps to Reproduce:

          1. Run oc adm must-gather
    2. Wait for it to complete
    3.

      Actual results:

          For a cluster with around 50 nodes, the must-gather took about 30 minutes.

      Expected results:

         For a cluster with around 50 nodes, the must-gather can finish in about 10 minutes.

      Additional info:

          It seems the gather_ppc collection script is related here.

https://github.com/openshift/must-gather/blob/release-4.14/collection-scripts/gather_ppc

              msivak@redhat.com Martin Sivak
              rhn-support-yhe Yiyong He
              Mallapadi Niranjan Mallapadi Niranjan
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: