Nick Vladiceanu

This does not seem a Solr Operator issue, perhaps makes sense to migrate this issue to [Solr Jira](https://issues.apache.org/jira/projects/SOLR/issues) workspace or ask the [community](https://solr.apache.org/community.html).

🙌 thanks for all the effort

> Scylla tries to allocate 52 GiB: > > ``` > >>> 0x1dc200000 * 7 / (1024**3) > 52.076171875 > ``` Yes, when Scylla Pod starts, the memory utilization is...

> Since this is EKS and Operator is in place, are you specifying `scyllaArgs` in your [Scylla Cluster CRD](https://operator.docs.scylladb.com/stable/scylla_cluster_crd.html)? In particular, I have seem an OOM situation recently, and it...

> Please capture /proc/.../smaps instead, it has additional information. From the capture above, the heap looks fine, but maybe the memory leaked somewhere else. sure, attached it below. Thank you...

hello @fee-mendes // @avikivity, I've passed `--memory XXG --lock-memory` arguments to the Scylla process but unfortunately the result is still the same, memory slowly increases over time. Please let me...

```bash # grep Rss: jmx_smaps.txt | sort -k2nr | tail -n +30 | awk ' { s += $2 } END { print s } ' 3336 ``` and ```bash...

The memory grows continuously, sharing the screenshot: Sharing here the screenshot of `top -o %MEM`: Also, here is the scylla-jmx VM summary:

> Also the CPU is high for the operator. In a steady state the starter binary is at almost 0% cpu and around 40MiB. Initially I thought this could be...

There are two major differences between `airflow-exporter` and `StatsD`: - StatsD setup is more complex, requires an additional exporter, and not so much support from the Official Helm chart; airflow-exporter...