Node C Node D TiKV-3 PingCAP.com Automatic Failover - A store is marked Down by PD when it’s unreachable for 30m (by default) - A store is marked Failed by TiDB Operator when it’s Down for 5m (by default)

TiKV_server_report_failure_msg_total • Alert rule: sum(rate(tikv_server_report_failure_msg_total{type="unreachable"}[10m]) �→ )BY (store_id)> 10 • Description: Indicates that the remote TiKV cannot be connected default. If you want to troubleshoot young GC issues, you can adjust mat configuration to view unreachable objects. In addition, for investigating the memory allocation of young GC issues (or a large number can run in one of the following statuses: • Up: The component is running normally. • Down or Unreachable: The component is not running or a network problem exists on the corresponding host. • Tombstone:

TiKV_server_report_failure_msg_total • Alert rule: sum(rate(tikv_server_report_failure_msg_total{type="unreachable"}[10m]) �→ )BY (store_id)> 10 • Description: Indicates that the remote TiKV cannot be connected default. If you want to troubleshoot young GC issues, you can adjust mat configuration to view unreachable objects. In addition, for investigating the memory allocation of young GC issues (or a large number can run in one of the following statuses: • Up: The component is running normally. • Down or Unreachable: The component is not running or a network problem exists on the corresponding host. • Tombstone:

TiKV_server_report_failure_msg_total • Alert rule: sum(rate(tikv_server_report_failure_msg_total{type="unreachable"}[10m]) �→ )BY (store_id)> 10 • Description: Indicates that the remote TiKV cannot be connected default. If you want to troubleshoot young GC issues, you can adjust mat configuration to view unreachable objects. In addition, for investigating the memory allocation of young GC issues (or a large number can run in one of the following statuses: • Up: The component is running normally. • Down or Unreachable: The component is not running or a network problem exists on the corresponding host. • Tombstone:

TiKV_server_report_failure_msg_total • Alert rule: sum(rate(tikv_server_report_failure_msg_total{type="unreachable"}[10m]) �→ )BY (store_id)> 10 • Description: Indicates that the remote TiKV cannot be connected default. If you want to troubleshoot young GC issues, you can adjust mat configuration to view unreachable objects. In addition, for investigating the memory allocation of young GC issues (or a large number can run in one of the following statuses: • Up: The component is running normally. • Down or Unreachable: The component is not running or a network problem exists on the corresponding host. • Tombstone:

TiKV_server_report_failure_msg_total • Alert rule: sum(rate(tikv_server_report_failure_msg_total{type="unreachable"}[10m]) �→ )BY (store_id)> 10 • Description: Indicates that the remote TiKV cannot be connected default. If you want to troubleshoot young GC issues, you can adjust mat configuration to view unreachable objects. In addition, for investigating the memory allocation of young GC issues (or a large number can run in one of the following statuses: • Up: The component is running normally. • Down or Unreachable: The component is not running or a network problem exists on the corresponding host. • Tombstone:

TiKV_server_report_failure_msg_total • Alert rule: sum(rate(tikv_server_report_failure_msg_total{type="unreachable"}[10m]) �→ )BY (store_id)> 10 • Description: Indicates that the remote TiKV cannot be connected default. If you want to troubleshoot young GC issues, you can adjust mat configuration to view unreachable objects. In addition, for investigating the memory allocation of young GC issues (or a large number can run in one of the following statuses: • Up: The component is running normally. • Down or Unreachable: The component is not running or a network problem exists on the corresponding host. • Tombstone:

TiKV_server_report_failure_msg_total • Alert rule: sum(rate(tikv_server_report_failure_msg_total{type="unreachable"}[10m]) �→ )BY (store_id)> 10 • Description: Indicates that the remote TiKV cannot be connected default. If you want to troubleshoot young GC issues, you can adjust mat configuration to view unreachable objects. In addition, for investigating the memory allocation of young GC issues (or a large number can run in one of the following statuses: • Up: The component is running normally. • Down or Unreachable: The component is not running or a network problem exists on the corresponding host. • Tombstone:

TiKV_server_report_failure_msg_total • Alert rule: sum(rate(tikv_server_report_failure_msg_total{type="unreachable"}[10m]) �→ )BY (store_id)> 10 • Description: Indicates that the remote TiKV cannot be connected default. If you want to troubleshoot young GC issues, you can adjust mat configuration to view unreachable objects. In addition, for investigating the memory allocation of young GC issues (or a large number can run in one of the following statuses: • Up: The component is running normally. • Down or Unreachable: The component is not running or a network problem exists on the corresponding host. • Tombstone:

TiKV_server_report_failure_msg_total • Alert rule: sum(rate(tikv_server_report_failure_msg_total{type="unreachable"}[10m]) �→ )BY (store_id)> 10 • Description: Indicates that the remote TiKV cannot be connected default. If you want to troubleshoot young GC issues, you can adjust mat configuration to view unreachable objects. In addition, for investigating the memory allocation of young GC issues (or a large number can run in one of the following statuses: • Up: The component is running normally. • Down or Unreachable: The component is not running or a network problem exists on the corresponding host. • Tombstone: