Bug 1494416 - The logging_mux_memory_limit is different with the default value
Summary: The logging_mux_memory_limit is different with the default value
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.6.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Petr Kovar
QA Contact: Vikram Goyal
Petr Kovar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-22 08:39 UTC by Anping Li
Modified: 2021-08-10 15:03 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-10 15:03:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHDEVDOCS-3090 0 Unprioritized Open Bug 1494416 - The logging_mux_memory_limit is different with the default value 2021-06-17 18:12:18 UTC

Description Anping Li 2017-09-22 08:39:03 UTC
Document URL: 
https://docs.openshift.com/container-platform/3.6/install_config/aggregate_logging.html#aggregated-fluentd

Section Number and Name: 
Reducing the Number of Connections from Fluentd to the API Server 

tables:
   openshift_logging_mux_memory_limit | 1Gi

Describe the issue: 

According to test [1], the default is 2Gi. 


Suggestions for improvement: 

tables:
   openshift_logging_mux_memory_limit | 2Gi




Additional information: 



[1]   Test Result:
        image: registry.test.com/test6/logging-fluentd:v3.6.0.6
        imagePullPolicy: Always
        name: mux
        ports:
        - containerPort: 24284
          name: mux-forward
          protocol: TCP
        resources:
          limits:
            cpu: 500m
            memory: 2Gi
          requests:
            memory: 2Gi


Note You need to log in before you can comment on or make changes to this bug.