{
  "index": {
    "refresh_interval": "1s",
    "number_of_shards": 1,
    "number_of_replicas": 0,
    "auto_expand_replicas": "0-1"
  },
  "analysis" : {
    "tokenizer" : {
      "fess_japanese_normal" : {
        "type" : "kuromoji_tokenizer",
        "mode" : "normal",
        "discard_punctuation" : "false"
      },
      "fess_korean_normal": {
        "type": "seunjeon_tokenizer",
        "index_eojeol": false,

{
  "index": {
    "refresh_interval": "1s",
    "number_of_shards": 1,
    "number_of_replicas": 0,
    "auto_expand_replicas": "0-1"
  },
  "analysis" : {
    "tokenizer" : {
      "fess_japanese_normal" : {
        "type" : "kuromoji_tokenizer",
        "mode" : "normal",
        "discard_punctuation" : "false"
      },
      "fess_korean_normal": {
        "type": "nori_tokenizer",
        "decompound_mode": "mixed",

{
  "index": {
    "refresh_interval": "1s",
    "number_of_shards": 1,
    "number_of_replicas": 0,
    "auto_expand_replicas": "0-1"
  },
  "analysis" : {
    "tokenizer" : {
      "fess_japanese_normal" : {
        "type" : "fess_japanese_tokenizer",
        "mode" : "normal",
        "discard_punctuation" : "false"
      },
      "fess_korean_normal": {
        "type": "fess_korean_tokenizer",
        "decompound_mode": "mixed",

    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.

If you use an old version kubectl to delete a replication controller or replicaset, then after the delete command has returned, the replication controller or the replicaset will continue to exist in the key-value store for a short period of time (<1s). You probably will not notice any difference if you use kubectl manually, but you might notice it if you are using kubectl in a script.

### DELETE operation in REST API

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

a(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:progress-bar-stripes 1s linear infinite;animation:progress-bar-stripes 1s linear infinite}@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}.media-body{-ms-flex:1...

a(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:progress-bar-stripes 1s linear infinite;animation:progress-bar-stripes 1s linear infinite}@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}.media-body{-ms-flex:1...

delay=0s,period=15s,failureThreshold=4. # This ensures the pod is marked ready immediately after the startup probe passes (which has a 1s poll interval), # and doesn't spam the readiness endpoint too much # # If the probe is disabled, it is recommended to have delay=1s,period=2s,failureThreshold=30. # This ensures the startup is reasonable fast (polling every 2s). 1s delay is used since the startup is not often ready instantly. startupProbe: enabled: true failureThreshold: 600 # 10 minutes # Resources...

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