ar-gradient(45deg,rgba(255,255,255,.15) 25%,transparent 25%,transparent 50%,rgba(255,255,255,.15) 50%,rgba(255,255,255,.15) 75%,transparent 75%,transparent);background-size:1rem 1rem}.progress-bar-animated{-webkit-animation:1s linear infinite progress-bar-stripes;animation:1s linear infinite progress-bar-stripes}@media (prefers-reduced-motion:reduce){.progress-bar-animated{-webkit-animation:none;animation:none}}.media{display:-ms-flexbox;display:flex;-ms-flex-align:start;align-items:flex-start}....

{
  "settings": {
    "index": {
      "codec": "${fess.index.codec}",
      "refresh_interval": "1s",
      "number_of_shards": "${fess.index.number_of_shards}",
      "number_of_replicas": 0,
      "auto_expand_replicas": "${fess.index.auto_expand_replicas}"
    },
    "analysis": {
      "char_filter": {
        "mapping_fa_filter": {
          "type": "mapping",

{
  "settings": {
    "index": {
      "codec": "${fess.index.codec}",
      "refresh_interval": "1s",
      "number_of_shards": "${fess.index.number_of_shards}",
      "number_of_replicas": 0,
      "auto_expand_replicas": "${fess.index.auto_expand_replicas}"
    },
    "analysis": {
      "char_filter": {
        "mapping_fa_filter": {
          "type": "mapping",

- Ensure Job status updates are batched by 1s. This fixes an unlikely scenario when a sequence of immediately 

    server.enqueue(
      MockResponse
        .Builder()
        .body("def")
        .throttleBody(1, 750, TimeUnit.MILLISECONDS)
        .build(),
    )

    // First request: time out after 1s.
    client =
      client
        .newBuilder()
        .readTimeout(Duration.ofSeconds(1))
        .build()
    executeSynchronously("/a").assertBody("abc")

    // Second request: time out after 250ms.

- Fixes error handling in a kubectl method used in downstream...

read this before you upgrade)

- Added the ability to reduce both the initial delay and the maximum delay accrued between container restarts for a node for containers in `CrashLoopBackOff` across the cluster to the recommended values of `1s` initial delay and `60s` maximum delay. To set this for a node, turn on the feature gate `ReduceDefaultCrashLoopBackOffDecay`. If you are also using the feature gate `KubeletCrashLoopBackOffMax` with a configured per-node `CrashLoopBackOff.MaxContainerRestartPeriod`,...

- A kubelet parameter and config option has been added to change the CFS quota period from the default 100ms to some other value between 1µs and 1s. This was done to improve response latencies for workloads running in clusters with guaranteed and burstable QoS classes. ([#63437](https://github.com/kubernetes/kubernetes/pull/63437), [@szuecs](https://github.com/szuecs)) Courtesy of SIG API Machinery,...

- GRPC probes now set a linger option of 1s to improve the TIME-WAIT state. ([#115321](https://github.com/kubernetes/kubernetes/pull/115321), [@rphillips](https://github.com/rphillips)) [SIG Network and Node]

backoff delay accrued between container restarts for a node for containers in `CrashLoopBackOff`. To set this for a node, turn on the feature gate `KubeletCrashLoopBackoffMax` and set the `CrashLoopBackOff.MaxContainerRestartPeriod ` field between `"1s"` and `"300s"` in your [kubelet config file](https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/). ([#128374](https://github.com/kubernetes/kubernetes/pull/128374), [@lauralorenz](https://github.com/lauralorenz)) [SIG API Machinery...