BitSail is a distributed high-performance data integration engine which supports batch, streaming and incremental scenarios. BitSail is widely used to synchronize hundreds of trillions of data every day.
When we submit a task using Bitsail, Bitsail initiates two processes: "Entry" and "CliFrontend." If we don't specify Java program parameters, they default to setting the Java heap memory (Xmx) to 1/4 of the maximum server memory when they start. This behavior is not container-friendly when using the Bitsail client, as it may lead to container Out of Memory (OOM) issues. We should have some limitations in place.
Flink provides the FLINK_ENV_JAVA_OPTS_CLI environment variable to set the memory usage for CliFrontend. However, Bitsail does not offer a similar configuration. This pull request introduces the BITSAIL_JAVA_OPTS configuration to restrict the memory and other related resources used by Bitsail processes.
When we submit a task using Bitsail, Bitsail initiates two processes: "Entry" and "CliFrontend." If we don't specify Java program parameters, they default to setting the Java heap memory (Xmx) to 1/4 of the maximum server memory when they start. This behavior is not container-friendly when using the Bitsail client, as it may lead to container Out of Memory (OOM) issues. We should have some limitations in place.
Flink provides the
FLINK_ENV_JAVA_OPTS_CLIenvironment variable to set the memory usage for CliFrontend. However, Bitsail does not offer a similar configuration. This pull request introduces theBITSAIL_JAVA_OPTSconfiguration to restrict the memory and other related resources used by Bitsail processes.