Status

Current state: Under Discussion

Discussion thread: https://lists.apache.org/thread/g4vl8mgnwgl7vjyvjy6zrc8w54b2lthv

Vote thread: https://lists.apache.org/thread/gcvv1x8j0kk8ngbmp9fbzcyrt83zym4p

JIRA: Unable to render Jira issues macro, execution error.

Released: 1.19

Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).

Motivation

The SQL Gateway is an essential component of Flink in OLAP scenarios, and its performance and stability determine the SLA of Flink as an OLAP service. Just like other components in Flink, we propose adding a separate configuration option to specify the Java options for the SQL Gateway. This would allow users to fine-tune the memory settings, garbage collection behavior, and other relevant Java parameters specific to the SQL Gateway, ensuring optimal performance and stability in production environments.

Public Interfaces

Introduce new configuration settings "env.java.opts.sql-gateway", represents the Java options to start the JVM of the SQL Gateway with.

Proposed Changes

The proposed "env.java.opts.sql-gateway" configuration option would take effect in a straightforward manner and be completely consistent with existing configuration options like "env.java.opts.taskmanager".

Test Plan

A manual validation is required to ensure that the configuration is taking effect, but it might not be necessary to add an additional end-to-end test specifically for this purpose.