The schedule.max-store-down-time parameter cannot be modified using tiup cluster edit-config, and the documentation should clarify this

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: schedule.max-store-down-time 参数不能用tiup cluster edit-config 去修改，文档应该说明

| username: Raymond

New Documentation Request, please provide feedback according to the template below:

  • Request Type: New Documentation
  • Background: The schedule.max-store-down-time PD configuration parameter cannot actually be modified using tiup cluster edit-config. The documentation should clarify that the correct method to modify this parameter is by connecting to PD using pd-ctl and executing the command config set max-store-down-time 30m. The official documentation does not currently indicate this, leading users to believe that this parameter can be modified like other parameters using tiup cluster edit-config. It is hoped that the official documentation can clarify this point.
  • Expected additions to the documentation and where to add them in the existing documentation:
    The official documentation does not currently indicate this, leading users to believe that this parameter can be modified like other parameters using tiup cluster edit-config. It is hoped that the official documentation can clarify this point.
    image
    image1132×172 8.44 KB
2
| username: Billmay表妹 | Original post link

The request has been forwarded~ I will update you with the progress.

3
| username: Billmay表妹 | Original post link

The specific progress can be seen in this PR: Add a notice for pd configuration by rleungx · Pull Request #12674 · pingcap/docs-cn · GitHub

4
| username: Raymond | Original post link

Thanks, cousin.

5
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.