Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-4597

Modify vector buffer and request to have fluentd parity

XMLWordPrintable

    • 1
    • False
    • None
    • False
    • NEW
    • NEW
    • Hide
      Prior to this change, vector collector deployments relied upon the default retry and buffering behavior. This could lead to the delivery pipeline being backed up trying to deliver every message when the availability of an output was unstable. This fix modifies the configuration to have parity with earlier releases of alternate collectors to limit the number of message retries and to drop messages once the threshold is exceeded.
      Show
      Prior to this change, vector collector deployments relied upon the default retry and buffering behavior. This could lead to the delivery pipeline being backed up trying to deliver every message when the availability of an output was unstable. This fix modifies the configuration to have parity with earlier releases of alternate collectors to limit the number of message retries and to drop messages once the threshold is exceeded.
    • Enhancement
    • Proposed
    • Log Collection - Sprint 243

      Summary

      The fluent collector was modified in a prior release (5.6?) to discard undeliverable messages after a configured time period (1h) in order to not block delivery pipelines. The default behavior of vector is to block and try indefinitely in order to not lose any messages. We believe this has lead to reported issues of high CPU and memory utilization, ref: LOG-4518, LOG-4536, LOG-4561

      Acceptance Criteria

      • Verify messages to an output that goes up and down are either delivered or dropped and messages continue to flow

        1. screenshot-1.png
          30 kB
          Jeffrey Cantrill

              jcantril@redhat.com Jeffrey Cantrill
              jcantril@redhat.com Jeffrey Cantrill
              Anping Li Anping Li
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: