TisonKun edited a comment on issue #10143: [FLINK-13184]Starting a TaskExecutor blocks the YarnResourceManager's main thread URL: https://github.com/apache/flink/pull/10143#issuecomment-553801831 I get your point now @wangyang0918 . One question, I see the only different between jm conf and tm conf is configured by ```java public static Configuration cloneConfiguration(Configuration configuration) { final Configuration clonedConfiguration = new Configuration(configuration); if (clonedConfiguration.getBoolean(USE_LOCAL_DEFAULT_TMP_DIRS)){ clonedConfiguration.removeConfig(CoreOptions.TMP_DIRS); clonedConfiguration.removeConfig(USE_LOCAL_DEFAULT_TMP_DIRS); } return clonedConfiguration; } ``` other configurations are all the same. Is it correct? I'm thinking a way just neither use dynamic properties nor ship another conf file at all. Because as @walterddr mentioned, we still encode jm config into dynamic properties, which possibly a huge string.
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
