- Sort Score
- Result 10 results
- Languages All
Results 341 - 350 of 379 for queued (0.17 sec)
-
CHANGELOG/CHANGELOG-1.27.md
- Sometimes, the scheduler incorrectly placed a pod in the "unschedulable" queue instead of the "backoff" queue. This happened when some plugin previously declared the pod as "unschedulable" and then in a later attempt encounters some other error. Scheduling of that pod then got delayed by up to five minutes, after which periodic flushing moved the pod back into the "active" queue. ([#120334](https://github.com/kubernetes/kubernetes/pull/120334), [@pohly](https://github.com/pohly))...
Registered: Fri Dec 26 09:05:12 UTC 2025 - Last Modified: Wed Jul 17 07:48:22 UTC 2024 - 466.3K bytes - Viewed (2) -
CHANGELOG/CHANGELOG-1.25.md
- Sometimes, the scheduler incorrectly placed a pod in the "unschedulable" queue instead of the "backoff" queue. This happened when some plugin previously declared the pod as "unschedulable" and then in a later attempt encounters some other error. Scheduling of that pod then got delayed by up to five minutes, after which periodic flushing moved the pod back into the "active" queue. ([#120334](https://github.com/kubernetes/kubernetes/pull/120334), [@pohly](https://github.com/pohly))...
Registered: Fri Dec 26 09:05:12 UTC 2025 - Last Modified: Mon May 06 09:23:20 UTC 2024 - 419.1K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.26.md
- Sometimes, the scheduler incorrectly placed a pod in the "unschedulable" queue instead of the "backoff" queue. This happened when some plugin previously declared the pod as "unschedulable" and then in a later attempt encounters some other error. Scheduling of that pod then got delayed by up to five minutes, after which periodic flushing moved the pod back into the "active" queue. ([#120334](https://github.com/kubernetes/kubernetes/pull/120334), [@pohly](https://github.com/pohly))...
Registered: Fri Dec 26 09:05:12 UTC 2025 - Last Modified: Thu Mar 14 16:24:51 UTC 2024 - 425.7K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.32.md
- Fixes the bug in PodTopologySpread that only happens with QHint enabled,
Registered: Fri Dec 26 09:05:12 UTC 2025 - Last Modified: Tue Dec 16 18:27:41 UTC 2025 - 448.1K bytes - Viewed (0) -
.bazelrc
# CUDA: This config refers to building CUDA op kernels with clang. common:cuda_clang --config=cuda common:cuda_clang --@local_config_cuda//:cuda_compiler=clang common:cuda_clang --copt=-Qunused-arguments # Select supported compute capabilities (supported graphics cards). # This is the same as the official TensorFlow builds. # See https://developer.nvidia.com/cuda-gpus#compute
Registered: Tue Dec 30 12:39:10 UTC 2025 - Last Modified: Fri Dec 26 23:20:26 UTC 2025 - 56.8K bytes - Viewed (0) -
android/guava/src/com/google/common/collect/Sets.java
import org.jspecify.annotations.NonNull; import org.jspecify.annotations.Nullable; /** * Static utility methods pertaining to {@link Set} instances. Also see this class's counterparts * {@link Lists}, {@link Maps} and {@link Queues}. * * <p>See the Guava User Guide article on <a href= * "https://github.com/google/guava/wiki/CollectionUtilitiesExplained#sets">{@code Sets}</a>. * * @author Kevin Bourrillion * @author Jared LevyRegistered: Fri Dec 26 12:43:10 UTC 2025 - Last Modified: Mon Sep 22 18:35:44 UTC 2025 - 81.6K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.30.md
- Previously, the scheduling queue didn't notice any extenders' failures, potentially resulting in missed cluster events and Pods rejected by Extenders being stuck in the unschedulable pod pool for up to 5 minutes in the worst-case scenario. Now, the scheduling queue notices extenders' failures and requeues Pods rejected by Extenders appropriately.
Registered: Fri Dec 26 09:05:12 UTC 2025 - Last Modified: Wed Jun 18 18:59:10 UTC 2025 - 398.1K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.22.md
- apiserver_flowcontrol_current_r: R(the time of the last change in state of the queues) - apiserver_flowcontrol_dispatch_r: R(the time of the latest request dispatch) - apiserver_flowcontrol_latest_s: S(the request last dispatched) = R(when that request starts executing in the virtual world) - apiserver_flowcontrol_next_s_bounds: min and max next S among non-empty queues
Registered: Fri Dec 26 09:05:12 UTC 2025 - Last Modified: Tue Dec 13 12:43:45 UTC 2022 - 454.1K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.14.md
### Scheduling - Improved fairness of the scheduling queue by placing pods which are attempted recently behind other pods with the same priority. ([#73700](https://github.com/kubernetes/kubernetes/pull/73700), [@denkensk](https://github.com/denkensk))
Registered: Fri Dec 26 09:05:12 UTC 2025 - Last Modified: Mon Jun 14 22:06:39 UTC 2021 - 271.5K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.3.md
* Change default value of deleting-pods-burst to 1 ([#27606](https://github.com/kubernetes/kubernetes/pull/27606), [@gmarek](https://github.com/gmarek)) * MESOS: fix race condition in contrib/mesos/pkg/queue/delay ([#24916](https://github.com/kubernetes/kubernetes/pull/24916), [@jdef](https://github.com/jdef))
Registered: Fri Dec 26 09:05:12 UTC 2025 - Last Modified: Thu Dec 24 02:28:26 UTC 2020 - 84K bytes - Viewed (0)