-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
daemon: add new option --allocator-list-timeout #15538
daemon: add new option --allocator-list-timeout #15538
Conversation
Hi there, please see the commit message for the purpose of this patch. Any comments welcomed. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR! Could you update the documentation with the new option please? Should be just a matter of running make -C Documentation update-cmdref check
and mentioning it in the upgrade document.
9ccaddf
to
607f788
Compare
Documentation updated, thanks! @jibi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thank you!
@ArthurChiao there seems to be some issues with the CI, could you rebase your PR on top of master? |
The Travis error seems related?
|
I'll take a look, thank you! |
607f788
to
92604aa
Compare
92604aa
to
d15ab81
Compare
Yes, unittests skipped the |
d15ab81
to
dda95eb
Compare
test-me-please |
dda95eb
to
de93f58
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought I had reviewed this PR but I guess not... @ArthurChiao the clustermesh-apiserver/main.go
likely needs this flag as well since it also uses the pkg/allocator/allocator.go
cc @jrajahalme
I'll take a look, thanks! @aanm |
This enables user to configure how long they would like to wait before successfully listed objects from kvstore. Especially, this determines the agent restart frequency when clustermesh is enabled and remote kvstore has connection problems: too many restarts in really large clusters pose significant pressures on both k8s apiserver, local and remote kvstores. Signed-off-by: ArthurChiao <arthurchiao@hotmail.com>
de93f58
to
3a9c0af
Compare
Checked that the calling stack is: Code updated, please have a review, thanks! @aanm |
test-me-please |
This enables user to configure how long they would like to wait before
successfully listed objects from kvstore. Especially, this determines the
agent restart frequency when clustermesh is enabled and remote kvstore
has connection problems: too many restarts in really large clusters pose
significant pressures on both k8s apiserver, local and remote kvstores.
Signed-off-by: ArthurChiao arthurchiao@hotmail.com