volcano
volcano copied to clipboard
feat(outOfSync): tracks and re-synchronizes node when it becomes 'OutOfSync'
- fix #1818.
- A possible fix to the above issue:
- Add a
RateLimitingQueueto holds the not ready nodes and start a asynchronous thread to synchronize them. - The events of
updateNodeandremoveTaskwill trigger the re-synchronization of the related nodes. - The synchronization of node will use the latest
v1.Nodeandv1.Podlist( a list of pods located on the former node) from the informer cache to:- updates node;
- removes unwanted tasks(unlikely) and adds missing tasks;
- Add a
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
/cc @shinytang6 @william-wang
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
/assign @Thor-wl @k82cn @shinytang6 @william-wang
@eggiter Please help resolve the conflicts. Thanks!
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign k82cn
You can assign the PR to them by writing /assign @k82cn in a comment when ready.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@eggiter Please help resolve the conflicts. Thanks!
Resolved. This is an important fix as discussed in https://github.com/volcano-sh/volcano/issues/1818#issuecomment-1102257005. PTAL! @Thor-wl @k82cn
OK. Let me take a review recently. Thanks!
@Thor-wl @k82cn
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.