fix(sync): delete complete worker pod when progressing & add more concurrent options#30
Merged
fix(sync): delete complete worker pod when progressing & add more concurrent options#30
Conversation
Member
zxh326
commented
Mar 19, 2025
zxh326
commented
- Delete the completed worker pod as soon as possible to avoid too many completed pods triggering kubelet limits.
- add more concurrent options
- add more log
Signed-off-by: Xuhui zhang <xuhui@juicedata.io>
zxh326
force-pushed
the
delete-complete-pod
branch
from
698156f to
6ae1912
Compare
Signed-off-by: Xuhui zhang <xuhui@juicedata.io>
zxh326
force-pushed
the
delete-complete-pod
branch
from
6ae1912 to
9e4fa86
Compare
Signed-off-by: Xuhui zhang <xuhui@juicedata.io>
zwwhdls
approved these changes
Mar 19, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.