bing0109 opened a new issue, #3617: URL: https://github.com/apache/incubator-streampark/issues/3617
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/incubator-streampark/issues?q=is%3Aissue+label%3A%22bug%22) and found no similar issues. ### Java Version 1.8 ### Scala Version 2.11.x ### StreamPark Version 2.1.2 ### Flink Version 1.18.1 ### deploy mode yarn-application ### What happened i create a flink job, and turn on the [Application Conf]，set 'jobmanager.memory.process.size' and 'taskmanager.memory.process.size' like the follow img, but it donot effective after i start the job.  when i set in the webUI ,it works normal  in the [flink Official website](https://nightlies.apache.org/flink/flink-docs-release-1.18/zh/docs/deployment/config/#memory-configuration), it describe as follow ```The default memory sizes support simple streaming/batch applications, but are too low to yield good performance for more complex applications. jobmanager.memory.process.size: Total size of the JobManager (JobMaster / ResourceManager / Dispatcher) process. taskmanager.memory.process.size: Total size of the TaskManager process. The total sizes include everything. Flink will subtract some memory for the JVM’s own memory requirements (metaspace and others), and divide and configure the rest automatically between its components (JVM Heap, Off-Heap, for Task Managers also network, managed memory etc.). These values are configured as memory sizes, for example 1536m or 2g. ``` so, why the config in [Application Conf] does not effective? ### Error Exception _No response_ ### Screenshots _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR!(您是否要贡献这个PR?) ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
