schema_version: 1
id: write-latency-during-concurrent-upsert
title: Write latency during concurrent upsert
status: draft
owner: codex
source: jira
environment:
  profile: stable-dedicated
  cluster_id: '10070106825815339119'
  cluster_type: dedicated
  tidb_version: unknown
time_window:
  incident_at: '2026-07-15T07:30:00Z'
  allowed:
  - id: reported_incident_window
    start: '2026-07-15T07:00:00Z'
    end: '2026-07-15T08:00:00Z'
prompt:
  text: 请分析 Dedicated 集群 10070106825815339119 在 2026-07-15T07:00:00Z 到 2026-07-15T08:00:00Z 的写入延迟和锁等待。业务会高并发 upsert 同一个投票聚合行，并在另一张表上维护多个二级索引。请判断热点、写放大和悲观锁之间的关系，并评估打散 key 或增加节点是否能解决问题。
tags:
- transaction
- write-latency
- hotspot
case_tier: P1
cost_tier: medium
followup:
  scheduled_max_followups: 0
execution:
  acp_bash_timeout_s: 900