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

gci-gce-scalability flakes - get configmaps latency issue #75171

Closed
krzysied opened this issue Mar 8, 2019 · 6 comments
Closed

gci-gce-scalability flakes - get configmaps latency issue #75171

krzysied opened this issue Mar 8, 2019 · 6 comments
Assignees
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability.

Comments

@krzysied
Copy link
Contributor

krzysied commented Mar 8, 2019

Which jobs are failing:
gci-gce-scalability - this is 100 nodes test for gce. This test is flaking.
Which test(s) are failing:
Density test

Since when has it been failing:
First fail can be seen in run 23438

Testgrid link:
https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gce-scalability/23438

Reason for failure:
99th percentile of GET configmaps call latency is greater than 1s.

Anything else we need to know:

@krzysied krzysied added the kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. label Mar 8, 2019
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Mar 8, 2019
@krzysied
Copy link
Contributor Author

krzysied commented Mar 8, 2019

/sig scalability

@k8s-ci-robot k8s-ci-robot added sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Mar 8, 2019
@krzysied
Copy link
Contributor Author

krzysied commented Mar 8, 2019

configmaps_latency

configmaps

It looks like the problem is related to the increased number of get configmaps call. When the get configmaps calls happen at the same time as saturation pods creation, their latencies significantly increase.

IIUC the increased number of get configmaps calls is due to #74755

@krzysied
Copy link
Contributor Author

krzysied commented Mar 8, 2019

#74755 should be only a temporary change. I expect that get configmap latency issue should resolve on its own.

/assign
I will try to debug it and find the bottleneck anyway.

@krzysied
Copy link
Contributor Author

krzysied commented Mar 8, 2019

/cc @mm4tt
/cc @wojtek-t

@wojtek-t
Copy link
Member

This #74781 should hopefully get it back to where we were previously.

@krzysied
Copy link
Contributor Author

krzysied commented Mar 18, 2019

configmaps_normal
It looks like it is fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability.
Projects
None yet
Development

No branches or pull requests

3 participants