wangyang0918 commented on issue #10143: [FLINK-13184]Starting a TaskExecutor blocks the YarnResourceManager's main thread URL: https://github.com/apache/flink/pull/10143#issuecomment-553861485 @TisonKun The differences between jm and tm config at least contains the followings. * `cloneConfiguration `, just as you say * `resourceManagerConfig.setString(TaskManagerOptions.LEGACY_MANAGED_MEMORY_SIZE, managedMemoryBytes + "b");` in `ActiveResourceManagerFactory` * `YarnEntrypointUtils#loadConfiguration` * `ClusterEntrypoint#initializeServices` * ... We just set the differences to dynamic properties. If your concern is we will get a huge start command, i think it will not happen since we do not update too many config options in jm side. @TisonKun @walterddr If you both still have the concern, maybe we need to split the PR into two optimizations.
---------------------------------------------------------------- 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
