Hi, Steven Regarding the term "active" in ActiveResourceManager, it signifies that it is responsible for actively creating and managing TaskManager instances based on requirements. It dynamically adjusts resources in the cluster, starting new TaskManager instances when needed.
On the other hand, StandaloneResourceManager is not considered "active" in the same sense as ActiveResourceManager because in standalone resource management mode, TaskManager instances need to be manually started by an external process and register themselves with the JobManager. Best, Junrui Yu Chen <yuchen.e...@gmail.com> 于2023年11月4日周六 12:06写道： > Hi Steven, > > As stated in the `StandaloneResourceManager` comments, the manager does > not acquire new resources and the user needs to manually start the > Taskmanager by themself. > While `ActiveResourceManager` achieves requesting or releasing resources > on demand(that's what active means) based on some resource frameworks ( > like yarn and k8s ). > > As we know, different users have different environments in production, and > not all of them want to run in yarn or k8s (especially for local debugging, > Standalone Cluster is very convenient). > Therefore, Flink provides users with these two different resource managers > to deal with different usage scenarios. > > Please feel free to correct me if there are any misunderstandings. > > Best regards, > Yu Chen > > Steven Chen <ghjsa_2...@163.com> 于2023年11月3日周五 13:28写道： > >> Dear Flink Community, >> >> >> I am currently using Flink for my project and have a question regarding >> ActiveResourceManager and StandaloneResourceManager. >> >> What does "active" mean in ActiveResourceManager and why is >> StandaloneResourceManager not considered an active resource manager? >> >> >> Thank you for your time and assistance. >> >> >> Best regards, >> Steven Chen >> >
