- Sort Score
- Num 10 results
- Language All
Results 1 - 2 of 2 for deallocator (0.1 seconds)
The search processing time has exceeded the limit. The displayed results may be partial.
-
src/main/resources/esclient.xml
<property name="settings"> {"http.cors.enabled":"true", "http.cors.allow-origin":"*", "discovery.type":"single-node", "cluster.allocator.existing_shards_allocator.batch_enabled":"true", <!-- "node.name":"search_engine", "discovery.seed_hosts":"search_engine", "cluster.initial_cluster_manager_nodes":"search_engine",
Created: Tue Mar 31 13:07:34 GMT 2026 - Last Modified: Sat Mar 28 06:59:19 GMT 2026 - 16.2K bytes - Click Count (0) -
CHANGELOG/CHANGELOG-1.33.md
- DRA: the explanation for why a pod which wasn't using ResourceClaims was unscheduleable included a useless "no new claims to deallocate" when it was unscheduleable for some other reasons. ([#129823](https://github.com/kubernetes/kubernetes/pull/129823), [@googs1025](https://github.com/googs1025)) [SIG Node and Scheduling]
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Thu Mar 19 03:17:58 GMT 2026 - 369K bytes - Click Count (0)