Assign WorkerGroup via worker configuration

[imbajin]

Currently, Vermeer Workers can be assigned to multiple WorkerGroups through the administrator REST API, thereby achieving parallel scheduling in different graph spaces.

In addition to this method, we would like to implement that when a new Worker is registered in the Master, it can be directly assigned to the specified WorkerGroup through the WorkerGroup name specified in the Worker configuration file.

[Ethereal-O]

Hello everyone, I have briefly outlined the calling process and related concepts such as Space, Graph, Worker, WorkerGroup, etc（ https://ethereal-o.github.io/2025/05/21/hugegraph-vermeer-reading/ ）.
Meanwhile, I also briefly outlined the plan for implementing this task:

1. Worker loads the WorkerGroup configuration item from the configuration at startup.
2. Pass configuration items to the Master when SayHello.
3. The Master uses the passed WorkerGroup configuration item in the CreateWorker function to assign a Group to the Worker.

At present, I think the points that need attention and solutions are as follows:

• Default configuration: Worker passes in a "$" string.
• Priority of recovery from object storage: The priority of recovery from object storage is higher, and I believe that ensuring the stability of the Master is the primary condition.
• Worker trustworthiness: Always believe that the worker is trustworthy and faithfully executing the correct code.

I would like to ask if my previous approach is correct? And are there any other areas that need attention? thank.

[hankwenyx]

Hello everyone, I have briefly outlined the calling process and related concepts such as Space, Graph, Worker, WorkerGroup, etc（ https://ethereal-o.github.io/2025/05/21/hugegraph-vermeer-reading/ ）. Meanwhile, I also briefly outlined the plan for implementing this task:

1. Worker loads the WorkerGroup configuration item from the configuration at startup.
2. Pass configuration items to the Master when SayHello.
3. The Master uses the passed WorkerGroup configuration item in the CreateWorker function to assign a Group to the Worker.

At present, I think the points that need attention and solutions are as follows:

• Default configuration: Worker passes in a "$" string.
• Priority of recovery from object storage: The priority of recovery from object storage is higher, and I believe that ensuring the stability of the Master is the primary condition.
• Worker trustworthiness: Always believe that the worker is trustworthy and faithfully executing the correct code.

I would like to ask if my previous approach is correct? And are there any other areas that need attention? thank.

Your approach is correct. And your code reading notes are very good, which can be further improved in detail to provide assistance to developers who will participate in the future.