You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the feature and found no similar feature requirement.
Description
At present, the Zeta engine does not distinguish between master nodes and worker nodes. All nodes can serve as master and worker nodes, and only one node in the entire cluster is marked as a master node at the same time. The master is responsible for receiving tasks submitted by clients and scheduling tasks, while also taking on the task running work.
When there are many tasks running in the cluster, the load on the master node can be very high, which may cause the master node to hang up and perform fault tolerance on the master node. Master node fault tolerance will further increase the responsibility of the cluster, especially newly selected master nodes have a greater chance of failure due to excessive load.
The goal of this proposal is to separate the roles of the master and worker nodes. The master node is only responsible for task scheduling, IMAP data storage, and access; Worker nodes are only responsible for the operation of tasks, and do not participate in the storage and access of IMAP data, nor do they participate in parameter elections.
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.
This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.
Search before asking
Description
At present, the Zeta engine does not distinguish between master nodes and worker nodes. All nodes can serve as master and worker nodes, and only one node in the entire cluster is marked as a master node at the same time. The master is responsible for receiving tasks submitted by clients and scheduling tasks, while also taking on the task running work.
When there are many tasks running in the cluster, the load on the master node can be very high, which may cause the master node to hang up and perform fault tolerance on the master node. Master node fault tolerance will further increase the responsibility of the cluster, especially newly selected master nodes have a greater chance of failure due to excessive load.
The goal of this proposal is to separate the roles of the master and worker nodes. The master node is only responsible for task scheduling, IMAP data storage, and access; Worker nodes are only responsible for the operation of tasks, and do not participate in the storage and access of IMAP data, nor do they participate in parameter elections.
Usage Scenario
No response
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: