- Sort Score
- Result 10 results
- Languages All
Results 1 - 5 of 5 for Queue (0.29 sec)
-
src/main/java/org/codelibs/fess/mylasta/direction/FessConfig.java
String INDEX_DOCUMENT_CRAWLER_INDEX = "index.document.crawler.index"; /** The key of the configuration. e.g. 10 */ String INDEX_DOCUMENT_CRAWLER_QUEUE_number_of_shards = "index.document.crawler.queue.number_of_shards"; /** The key of the configuration. e.g. 10 */ String INDEX_DOCUMENT_CRAWLER_DATA_number_of_shards = "index.document.crawler.data.number_of_shards";
Java - Registered: Mon May 06 08:04:11 GMT 2024 - Last Modified: Thu Apr 11 02:34:53 GMT 2024 - 459.2K bytes - Viewed (5) -
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))...
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Tue Apr 16 21:41:06 GMT 2024 - 299.9K bytes - Viewed (1) -
CHANGELOG/CHANGELOG-1.28.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))...
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Tue Apr 16 20:44:48 GMT 2024 - 385.1K bytes - Viewed (0) -
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))...
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Tue Apr 16 15:20:21 GMT 2024 - 434.3K bytes - Viewed (3) -
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))...
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Thu Mar 14 16:24:51 GMT 2024 - 425.7K bytes - Viewed (0)