Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-3326

Defaul value for MaxMetaspaceSize in Operator overrieds default values set by image scripts

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.10.0.GA
    • 7.9.1.GA
    • Cloud
    • None

    • OCP 4.6
      BA Operator 7.9.1

    • False
    • False
    • CR1
    • CR1
    • Undefined
    • Hide

      In case that users will run to failures caused by MaxMetaspaceSize they can override the default value of MaxMetaspaceSize in KieApp. Default value for BC image was 1024 in 7.9.0.

      Show
      In case that users will run to failures caused by MaxMetaspaceSize they can override the default value of MaxMetaspaceSize in KieApp. Default value for BC image was 1024 in 7.9.0.
    • Hide
      1. Start BA Operator
      2. Rung RHPAM Authoring app
      3. Check in KieApp yaml that jvm MaxMetaspaceSize value is set (not set while verifying fix or using previous versions)
      4. Check pods logs and there set MaxMetaspaceSize values, there should be everywhere 512m (if not set there should be values set based on memory limits, for details in config check jboss cct modules scripts)
      Show
      Start BA Operator Rung RHPAM Authoring app Check in KieApp yaml that jvm MaxMetaspaceSize value is set (not set while verifying fix or using previous versions) Check pods logs and there set MaxMetaspaceSize values, there should be everywhere 512m (if not set there should be values set based on memory limits, for details in config check jboss cct modules scripts)
    • ---
    • ---

    Description

      With new default value for MaxMetaspaceSize (env. var. GC_MAX_METASPACE_SIZE), added as part of RHPAM-3245, we are now disabling automated configuration of the JVM values for the OCP images. We already have default values for MaxMetaspaceSize set in jboss kie modules. For some images, e.g. Business Central is set MaxMetaspaceSize to 1024m, is MaxMetaspaceSize override to lower value.

      Places in jboss kie modules, where are set default values for images:
      https://github.com/jboss-container-images/jboss-kie-modules/blob/master/os-eap-legacy/os-eap7-openshift/added/standalone.conf#L4
      https://github.com/jboss-container-images/jboss-kie-modules/blob/master/jboss-kie-workbench/added/launch/jboss-kie-workbench.sh#L293

      We need to make clear where and to what is this value for MaxMetaspaceSize set.
      Probably the best would be to remove configuration of default value for MaxMetaspaceSize in Operator and just keep the one for images. We can probably increase the default value in standalone.conf file.

      Attachments

        Issue Links

          is documented by

          Task - Represents a small unit of work that is not end-user facing. BXMSDOC-7009 Update default value for `MaxMetaspaceSize`

          • 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

          Activity

            People

              tarkhand Tarun Khandelwal (Inactive)
              jakubschwan Jakub Schwan
              Jiri Simek Jiri Simek
              Jiri Simek Jiri Simek
              Filippe Spolti
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: