Uploaded image for project: 'Maistra'
  1. Maistra
  2. MAISTRA-681

Performance Issues when control plane has lots of namespaces

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Major
    • maistra-1.1.13
    • maistra-0.10.0
    • None
    • None
    • Sprint 1, Sprint 2, Sprint 3

    Description

      When the control plane has lots of namespaces, the namespace list is taking too long to be generated.

      On Kiali side, we observed the getNamespaceList can take 5 seconds with 2 namespaces on a control plane

      Some spikes of 5, 10 and even 20 seconds were observed with more namespaces

      Testing information:

      https://docs.google.com/presentation/d/1ZhKzsvu4iJNUHsnieVUEOYDV797Y40dSuPpjFF5sFJc/edit?usp=sharing

      Possibly related to kubernetes cache.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. MAISTRA-2246 Performance Issues when control plane has lots of namespaces

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is incorporated by

          Task - Represents a small unit of work that is not end-user facing. OSSM-123 Maistra - Address performance issues when control plane manages many namespaces

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. MAISTRA-2164 IOR queries

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          relates to

          Task - Represents a small unit of work that is not end-user facing. MAISTRA-2192 Concurrent reconciliation of member namespaces

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          links to

          GitHub openshift/openshift-docs#45652: OSSMDOC-467: Service Mesh 2.2 release notes

          Activity

            People

              yuaxu@redhat.com Yuanlin Xu
              rh-ee-gbaufake Guilherme Baufaker Rego
              Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: