Skip to content
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

make xds send timeout configurable #27687

Merged
merged 1 commit into from Oct 3, 2020

Conversation

ramaraochavali
Copy link
Contributor

We are seeing "2020-09-25T18:36:23.207985Z info ads Timeout writing sidecar~10.100.181.200" in some envs occasionally.

Making this configurable to test if it helps

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Pull Request Attributes

Please check any characteristics that apply to this pull request.

[X ] Does not have any changes that may affect Istio users.

Signed-off-by: Rama Chavali <rama.rao@salesforce.com>
@ramaraochavali ramaraochavali requested a review from a team as a code owner October 2, 2020 07:21
@istio-policy-bot istio-policy-bot added area/networking release-notes-none Indicates a PR that does not require release notes. labels Oct 2, 2020
@googlebot googlebot added the cla: yes Set by the Google CLA bot to indicate the author of a PR has signed the Google CLA. label Oct 2, 2020
@istio-testing istio-testing added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Oct 2, 2020
@ramaraochavali
Copy link
Contributor Author

/test unit-tests_istio

@istio-testing istio-testing merged commit 7f9f941 into istio:master Oct 3, 2020
@ramaraochavali ramaraochavali deleted the fix/xds_timeout branch October 3, 2020 05:06
@hzxuzhonghu
Copy link
Member

What is your env that this occurs, purely increase timeout may mask some real error.

@ramaraochavali
Copy link
Contributor Author

It happens on k8s 1.16. This only happens on dev clusters not on test/stage/prod. I suspect it is because of huge configurations sent because of number of services. I would like to see if this helps. Also I am thinking of adding a metric to record the send times - so that we can see how it is doing with various cluster sizes

@hzxuzhonghu
Copy link
Member

make sense

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/networking cla: yes Set by the Google CLA bot to indicate the author of a PR has signed the Google CLA. release-notes-none Indicates a PR that does not require release notes. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants