Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 20 for Queued (0.08 sec)

  1. CHANGELOG/CHANGELOG-1.28.md

      When the scheduling queue receives a cluster event, before moving each Pod from unschedulable pod pool to activeQ/backoffQ, it will call QueueingHintFn of plugins that rejected each Pod in the previous scheduling cycle.
      Depending on the value returned from QueueingHintFn, the scheduling queue changes how it queues each Pod:
      - if more than one QueueingHintFn returns QueueImmediately, it queues Pod to activeQ.
    Registered: Fri Nov 01 09:05:11 UTC 2024
    - Last Modified: Wed Oct 23 04:34:59 UTC 2024
    - 456.9K bytes
    - Viewed (0)
  2. CHANGELOG/CHANGELOG-1.15.md

    ### Alpha
    
    - You can now create a non-preempting Pod priority (NonPreemptingPriority). If set on a class, the pod will continue to be prioritized above queued pods of a lesser class, but will not preempt running pods. ([#74614](https://github.com/kubernetes/kubernetes/pull/74614), [@denkensk](https://github.com/denkensk))
    Registered: Fri Nov 01 09:05:11 UTC 2024
    - Last Modified: Thu May 05 13:44:43 UTC 2022
    - 278.9K bytes
    - Viewed (0)
  3. doc/go_spec.html

              [n]T, *[n]T      array length (== n)
              []T              slice length
              map[K]T          map length (number of defined keys)
              chan T           number of elements queued in channel buffer
              type parameter   see below
    
    cap(s)    [n]T, *[n]T      array length (== n)
              []T              slice capacity
              chan T           channel buffer capacity
    Registered: Tue Nov 05 11:13:11 UTC 2024
    - Last Modified: Wed Oct 02 00:58:01 UTC 2024
    - 282.5K bytes
    - Viewed (0)
  4. CHANGELOG/CHANGELOG-1.29.md

    Fixed a situation when, 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 Nov 01 09:05:11 UTC 2024
    - Last Modified: Wed Oct 23 04:37:31 UTC 2024
    - 375.1K bytes
    - Viewed (1)
  5. CHANGELOG/CHANGELOG-1.31.md

      Now, when unschedulable Pods are updated, the scheduling queue checks with QueueingHint(s) whether the update may make the pods schedulable, and requeues them to activeQ/backoffQ **only when** at least one QueueingHint(s) return Queue. 
      
      Action required for custom scheduler plugin developers:
    Registered: Fri Nov 01 09:05:11 UTC 2024
    - Last Modified: Wed Oct 23 12:18:32 UTC 2024
    - 315.4K bytes
    - Viewed (0)
  6. src/main/java/org/codelibs/fess/mylasta/direction/FessConfig.java

        /**
         * Get the value for the key 'index.document.crawler.queue.number_of_shards'. <br>
         * The value is, e.g. 10 <br>
         * @return The value of found property. (NotNull: if not found, exception but basically no way)
         */
        String getIndexDocumentCrawlerQueueNumberOfShards();
    
        /**
         * Get the value for the key 'index.document.crawler.queue.number_of_shards' as {@link Integer}. <br>
    Registered: Thu Oct 31 13:40:30 UTC 2024
    - Last Modified: Fri Oct 11 21:11:58 UTC 2024
    - 468.5K bytes
    - Viewed (1)
  7. 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 Nov 01 09:05:11 UTC 2024
    - Last Modified: Wed Jul 17 07:48:22 UTC 2024
    - 466.3K bytes
    - Viewed (0)
  8. 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 Nov 01 09:05:11 UTC 2024
    - Last Modified: Wed Oct 23 04:40:14 UTC 2024
    - 309.1K bytes
    - Viewed (0)
  9. 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 Nov 01 09:05:11 UTC 2024
    - Last Modified: Mon May 06 09:23:20 UTC 2024
    - 419.1K bytes
    - Viewed (0)
  10. 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 Nov 01 09:05:11 UTC 2024
    - Last Modified: Thu Mar 14 16:24:51 UTC 2024
    - 425.7K bytes
    - Viewed (0)
Back to top