---
schema_version: 1
id: throttle-refill-rate-verification-after-change-window
title: Throttle refill-rate verification after a premium config-change window
status: active
owner: codex
evaluation:
  mode: adhoc_evidence
environment:
  profile: stable-premium
  cluster_label: premium-resource-pool
  cluster_id: '2026948324023603200'
  cluster_type: premium
  tidb_version: v8.5.4
time_window:
  resolved_by_output: resolved_window
runtime:
  hooks:
  - id: resolve_runtime_window
    stage: before_acp
    kind: python_script
    path: runtime_hook.py
    output_id: resolved_window
    args:
    - resolve-window
  - id: build_reference_answer
    stage: before_judge
    kind: python_script
    path: runtime_hook.py
    output_id: reference_answer
    args:
    - build-reference
    - "--cluster-id"
    - "{{environment.cluster_id}}"
    - "--start"
    - "{{runtime.resolved_window.start}}"
    - "--end"
    - "{{runtime.resolved_window.end}}"
prompt:
  text: |
    帮我验证这个 Premium 资源池集群（`{{environment.cluster_id}}`）里，
    `resource-control.cpu-throttle.low-priority-dag-global-ratio`
    在北京时间 `2026-07-07 06:00` 改成 `0.5` 之后，是否真的已经生效到 TiKV。

    你只需要做“是否生效”的验证，不要扩展成完整 RCA。观察时间窗固定为：
    - `{{runtime.resolved_window.start}}` 到 `{{runtime.resolved_window.end}}`

    最终只输出一个 `json` 代码块，字段必须严格为：
    `cluster_id`、`window`、`requested_ratio`、`expected_refill_rate_us_per_interval`、`observed_refill_rate_us_per_interval`、`applied`、`evidence_sufficient`

    JSON 结构如下：

    ```json
    {
      "cluster_id": "2026948324023603200",
      "window": {
        "start": "2026-07-06T21:50:00Z",
        "end": "2026-07-07T01:00:00Z"
      },
      "requested_ratio": 0.5,
      "expected_refill_rate_us_per_interval": 1240000,
      "observed_refill_rate_us_per_interval": 992000,
      "applied": false,
      "evidence_sufficient": true
    }
    ```

    如果证据不足，请把：
    - `evidence_sufficient` 设为 `false`
    - `applied` 设为 `false`
    - 其他数值字段填 `null`

    不要输出额外字段，不要输出额外解释。
tags:
- premium
- config-check
- structured-output
- adhoc-evidence
case_tier: P1
cost_tier: low
followup:
  scheduled_max_followups: 0
execution:
  acp_bash_timeout_s: 300