yvesblt opened a new issue, #15069:
URL: https://github.com/apache/druid/issues/15069
### Affected Version
Version 25.0.0
### Description
We have observed that druid-cluster-broker are automatically restarted due
to outOfmemory java-heap memory and the pod restart because of OOMKilled error
137.
- Cluster size : 3 brokers with the following configuration:
```yaml
Limits:
cpu: 18
memory: 82Gi
Requests:
cpu: 9
memory: 41Gi
DRUID_MAXDIRECTMEMORYSIZE: 32000m
DRUID_XMS: 24576m
DRUID_XMX: 49152m
JAVA_OPTS: -XX:+UseG1GC
druid_broker_http_numConnections: 30
druid_processing_buffer_sizeBytes: 1073741824
druid_processing_numMergeBuffers: 16
druid_processing_numThreads: 16
druid_query_groupBy_maxOnDiskStorage: 5242880000
druid_server_http_numThreads: 40
druid_sql_enable: true
druid_sql_planner_metadataSegmentCacheEnable: true
druid_sql_planner_useApproximateTopN: false
```
Faulty behaviour:
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
