"cluster-logging-operator" pod keeps restarting with "fatal error: concurrent map read and map write" #2345
Labels
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
Describe the bug
Hello. We're facing an issue where the "cluster-logging-operator" pod has been restarted 100 times in the past 6 months, always with the same error "fatal error: concurrent map read and map write". Our openshift-logging is configured with a
ClusterLogging
and aClusterLogForwarder
forwarding logs to three Kafka brokers.Environment
Logs
cluster-logging-operator.log
Expected behavior
cluster-logging-operator
pod does not crash/restartActual behavior
Pod restarts after X amount of time
To Reproduce
Cannot consistently reproduce - pod crashes seemingly at random after X time
Additional context
Happy to provide additional info if necessary. Thank you.
The text was updated successfully, but these errors were encountered: