Comments (7)
Did your test actually get failed by this 30 min timeout?
No, I didn't. It's fair to reopen this when I get actually this situation. Thanks for your input.
from kubernetes.
This issue is currently awaiting triage.
If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
from kubernetes.
@kubernetes/sig-scheduling-approvers I'd be happy to contribute to this issue if it is acceptable.
from kubernetes.
User case is first, do you have any real case here.
from kubernetes.
Agree with @kerthcet. If you want to define a test case which takes more than 30 mins to finish, it feels like that's something undesired.
Additionally to say, even if there's a usecase (let's say using ~1 hour) actually, could we just extend the global timeout to 1 hour? I don't see any necessity of per-test timeout.
from kubernetes.
User case is first, do you have any real case here.
It's very important. Let me share my experience. Unfortunately, I know of a scheduler with fairly poor throughput. That is like an order of magnitude slower throughput. For example, a co-scheduling plugin would be something that could significantly reduce throughput. However, we would like to verify throughput and deadlock on a large number of nodes (possibly an endurance test). In this case, I think scheduler-perf is currently appropriate. However, it will take more than 30 minutes. If preemption is also included, there is an extra possibility of this.
Additionally to say, even if there's a usecase (let's say using ~1 hour) actually, could we just extend the global timeout to 1 hour? I don't see any necessity of per-test timeout.
Certainly, this could be the case. However, in the case of fast
label, for example, it is expected to fail quickly. In this case, it seems a bit wasteful to wait an hour for a deadlock or something
@kerthcet @sanposhiho Given your extensive experience, I would appreciate hearing your perspective. Could you please share your thoughts? 🙏
from kubernetes.
Even if the scheduler is 10 times slower (= 30 pods/s throughput),
the scheduler can handle 54000 scheduling cycles within 30 min theoretically.
Did your test actually get failed by this 30 min timeout? I mean, for example, didn't your test case include something mistaken and some Pods left unschedulable forever?
It sounds like too slow (as long as you used an appropriate sized test case), even if your test involves preemption.
from kubernetes.
Related Issues (20)
- kube-apiserver logs watch requests before they end in 1.30 HOT 10
- Node Lifecycle Controller does not mark pods not ready when node becomes Ready=False HOT 8
- endpoints cannot be changed from notReadyAddresses to addresses HOT 8
- Enhancement: Add vTPM Configuration Fields for Enhanced Container Security HOT 3
- 'kubectl delete istag/$ISTAG --dry-run=server' is unexpectedly deleting the object from the server HOT 5
- [FG:InPlacePodVerticalScaling] resources in pod status are never updated if EventedPLEG is enabled HOT 2
- [Flaking test] ci-kubernetes-e2e-gci-gce.Overall HOT 4
- `kubernetes.io/legacy-token-last-used` label being added to long lived service token secrets HOT 2
- The endpoint status does not update when the pod state changes rapidly. HOT 8
- Pod with exitCode 137, The reason has nothing to do with resources。 HOT 2
- Failure cluster [9afae275...] HOT 2
- finish DRA for 1.31 HOT 4
- [Failing Test] ci-kubernetes-cloud-provider-kind-conformance-parallel-ipv6 (client rate limiter error) HOT 2
- TypeMeta is empty in Type client Apply and Patch responses HOT 3
- Job API: Relax validation enforcing Pod Failure Policy is only compatible with pod restart policy of "Never" HOT 7
- invalid memory address or nil pointer dereference" in wait.JitterUntil HOT 4
- Performance Optimization for UpdateSnapshot when there is only one zone HOT 2
- Performance optimization for UpdateSnapshot method when there is only one zone HOT 4
- [Flaking Test] UT apiserver/pkg/storage: cacher for 3m timeout HOT 16
- [PSA] SHA-1 signature support fully going away in go1.24 HOT 11
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from kubernetes.