为提高效率,请提供以下信息,问题描述清晰能够更快得到解决:
【概述】
通过pd-ctl修改max-store-down-time为24小时
» config set max-store-down-time 24h
Success!
» config show max-store-down-time
{
“replication”: {
“enable-placement-rules”: “true”,
“location-labels”: “dc,host”,
“max-replicas”: 3,
“strictly-match-label”: “false”
},
“schedule”: {
“enable-cross-table-merge”: “false”,
“enable-debug-metrics”: “false”,
“enable-location-replacement”: “true”,
“enable-make-up-replica”: “true”,
“enable-one-way-merge”: “false”,
“enable-remove-down-replica”: “true”,
“enable-remove-extra-replica”: “true”,
“enable-replace-offline-replica”: “true”,
“high-space-ratio”: 0.7,
“hot-region-cache-hits-threshold”: 3,
“hot-region-schedule-limit”: 4,
“leader-schedule-limit”: 25,
“leader-schedule-policy”: “count”,
“low-space-ratio”: 0.8,
“max-merge-region-keys”: 200000,
“max-merge-region-size”: 20,
“max-pending-peer-count”: 16,
“max-snapshot-count”: 3,
"max-store-down-time": “24h0m0s”,
“merge-schedule-limit”: 8,
“patrol-region-interval”: “100ms”,
“region-schedule-limit”: 25,
“replica-schedule-limit”: 64,
“scheduler-max-waiting-operator”: 5,
“split-merge-interval”: “1h0m0s”,
“store-limit-mode”: “manual”,
“tolerant-size-ratio”: 0
}
}
查看修改后的参数,为24小时
mysql> show config where name=‘schedule.max-store-down-time’;
±-----±-----------------±-----------------------------±--------+
| Type | Instance | Name | Value |
±-----±-----------------±-----------------------------±--------+
| pd | xx.xx.xx.xx:2379 | schedule.max-store-down-time | 24h0m0s |
| pd | xx.xx.xx.xx:2379 | schedule.max-store-down-time | 24h0m0s |
| pd | xx.xx.xx.xx:2379 | schedule.max-store-down-time | 24h0m0s |
±-----±-----------------±-----------------------------±--------+
3 rows in set, 24 warnings (0.00 sec)
但是edit-config里面,没有发现该参数
pd:
replication.enable-placement-rules: true
replication.location-labels:
- dc
- host
schedule.leader-schedule-limit: 4
schedule.region-schedule-limit: 2048
schedule.replica-schedule-limit: 64
tiflash: {}
tiflash-learner: {}
并且pd.log里面还是默认的30分钟(集群已经重启过了)
“max-store-down-time”:"30m0s
请问这个参数到底修改成功了吗?
【背景】做过哪些操作
【现象】业务和数据库现象
【业务影响】
【TiDB 版本】
【附件】
- 相关日志 和 监控
-
TiUP Cluster Display 信息
-
TiUP Cluster Edit Config 信息
-
TiDB- Overview 监控
- 对应模块日志(包含问题前后1小时日志)
若提问为性能优化、故障排查类问题,请下载脚本运行。终端输出的打印结果,请务必全选并复制粘贴上传。