make CNITimeoutSec configurable #491
Open
Conversation
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
wsc-2025
requested review from
awmirantis,
mlimardo1984,
smerkviladze and
yevchuk-kostiantyn
as code owners
yevchuk-kostiantyn
requested changes
Jul 9, 2025
Collaborator
yevchuk-kostiantyn
left a comment
yevchuk-kostiantyn
left a comment
There was a problem hiding this comment.
Hi @wsc-2025,
Thanks for filing the PR.
Can you please create an issue, document why the existing const CNITimeoutSec = 220 is not enough in specific use-cases/scenarios, the suggested fix etc.?
Author
|
OK,this is the issue.#492. @yevchuk-kostiantyn |
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.
Fixes #
const CNITimeoutSec = 220 sometimes is not enough.
Proposed Changes
Maybe we shoud make CNITimeoutSec configurable.