MM-X-C opened a new issue, #16873:
URL: https://github.com/apache/iotdb/issues/16873

   In a Docker-based standalone deployment of IoTDB, setting MEMORY_SIZE (e.g., 
MEMORY_SIZE=4G) in iotdb-env.sh does not take effect. During startup, the 
compaction recovery process (specifically "recovering sequence inner 
compaction") causes the container memory usage to continuously increase without 
bound, eventually leading to OOM or high resource exhaustion. This prevents the 
RPC service from becoming available (connection refused on port 6667). The 
issue persists across versions 1.3.2 and 2.0.5, with no visible impact from the 
JVM heap configuration.
   This occurs in standalone mode. No errors are logged beyond the repeated 
recovery messages, and basic resource limits in docker-compose.yml (e.g., 
limits: memory: 6G) do not mitigate the growth.


-- 
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]

Reply via email to