Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-3518

AMQ 7 operator deployment - logs can consume entire disk

    XMLWordPrintable

Details

    Description

      If an application generates a lot of WARN log messages, for example if message re-delivery is exceeded during a performance test, the logs can consume the entire PV. For an operator deployment, there is currently no way to configure the logging either (to set up, for example, rolling logs).

      Attachments

        1. broker_activemqartemis_cr.yaml
          1 kB
        2. broker_logs
          14 kB
        3. configmap.yaml
          4 kB
        4. operator_logs
          324 kB
        5. operator.yaml
          17 kB

        Issue Links

          incorporates

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-6406 Allow to set loglevel at ActiveMQArtemis CR level

          • 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 cloned by

          Task - Represents a small unit of work that is not end-user facing. ENTMQBR-4624 Doc: AMQ 7 operator deployment - logs can consume entire disk

          • 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

          Task - Represents a small unit of work that is not end-user facing. ENTMQBR-5945 [doc] AMQ 7 operator deployment - logs can consume entire disk

          • 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 duplicated by

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-5469 [OpenShift] Artemis log is created inside the AMQ Broker Data folder

          • 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

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-7157 logging - fix defaults in the image to just use stdout - no disk

          • Undefined - Priority not specified.
          • Closed
          is related to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. ENTMQBR-3588 Allow configurable logging for AMQ 7 Operator Deployments

          • 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

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-7616 Exception java.security.PrivilegedActionException raised when the broker starts

          • 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

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-7877 [LTS] Exception java.security.PrivilegedActionException raised when the broker starts

          • 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
          mentioned in

          Page Loading...

          Page Loading...

          Activity

            People

              gaohoward Howard Gao
              rhn-support-shiggs Stephen Higgs
              Tiago Bueno Tiago Bueno
              Votes:
              2 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: