Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document pre/post upgrade and reload scripts #17611

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dveeden
Copy link
Contributor

@dveeden dveeden commented May 23, 2024

What is changed, added or deleted? (Required)

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

  • master (the latest development version)
  • v8.2 (TiDB 8.2 versions)
  • v8.1 (TiDB 8.1 versions)
  • v8.0 (TiDB 8.0 versions)
  • v7.6 (TiDB 7.6 versions)
  • v7.5 (TiDB 7.5 versions)
  • v7.1 (TiDB 7.1 versions)
  • v6.5 (TiDB 6.5 versions)
  • v6.1 (TiDB 6.1 versions)
  • v5.4 (TiDB 5.4 versions)
  • v5.3 (TiDB 5.3 versions)
  • v5.2 (TiDB 5.2 versions)
  • v5.1 (TiDB 5.1 versions)

What is the related PR or file link(s)?

  • This PR is translated from:
  • Other reference link(s):

pingcap/tiup#2130

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

Copy link

ti-chi-bot bot commented May 23, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign lichunzhu for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot bot added missing-translation-status This PR does not have translation status info. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels May 23, 2024
Copy link

ti-chi-bot bot commented May 27, 2024

@kaaaaaaang: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@qiancai qiancai self-assigned this May 28, 2024
@qiancai qiancai added the translation/doing This PR's assignee is translating this PR. label May 28, 2024
@ti-chi-bot ti-chi-bot bot removed the missing-translation-status This PR does not have translation status info. label May 28, 2024
@qiancai qiancai added area/tiup Indicates that the Issue or PR belongs to the area of the TiUP tool. needs-cherry-pick-release-8.0 Should cherry pick this PR to release-8.0 branch. needs-cherry-pick-release-8.1 Should cherry pick this PR to release-8.1 branch. labels May 28, 2024
Copy link
Collaborator

@qiancai qiancai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rest LGTM

Comment on lines +88 to +90
- Run a script before the reload.
- Data type: `STRINGS`
- This option specifies the path of the command that will be ran on the host that is to be reloaded.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Run a script before the reload.
- Data type: `STRINGS`
- This option specifies the path of the command that will be ran on the host that is to be reloaded.
- Runs a script before the reload.
- Data type: `STRINGS`
- This option specifies the path of a script to be run on the host that is to be reloaded.

Comment on lines +98 to +100
- Run a script after the reload.
- Data type: `STRINGS`
- This option specifies the path of the command that will be ran on the host that was reloaded.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Run a script after the reload.
- Data type: `STRINGS`
- This option specifies the path of the command that will be ran on the host that was reloaded.
- Runs a script after the reload.
- Data type: `STRINGS`
- This option specifies the path of a script to be run after the reload of a host.

Comment on lines +131 to +133
- Run a script before the upgrade.
- Data type: `STRINGS`
- This option specifies the path of the command that will be ran on the host that is to be upgraded.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Run a script before the upgrade.
- Data type: `STRINGS`
- This option specifies the path of the command that will be ran on the host that is to be upgraded.
- Runs a script before the upgrade.
- Data type: `STRINGS`
- This option specifies the path of a script to be run on the host that is to be upgraded.

Comment on lines +141 to +143
- Run a script after the upgrade.
- Data type: `STRINGS`
- This option specifies the path of the command that will be ran after the upgrade of a host. This command will be executed on the upgraded host itself.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Run a script after the upgrade.
- Data type: `STRINGS`
- This option specifies the path of the command that will be ran after the upgrade of a host. This command will be executed on the upgraded host itself.
- Runs a script after the upgrade.
- Data type: `STRINGS`
- This option specifies the path of a script to be run after the upgrade of a host. This command will be executed on the upgraded host itself.

Copy link

ti-chi-bot bot commented Jun 17, 2024

[LGTM Timeline notifier]

Timeline:

  • 2024-06-17 08:22:52.201851011 +0000 UTC m=+16698.687339843: ☑️ agreed by qiancai.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/tiup Indicates that the Issue or PR belongs to the area of the TiUP tool. needs-1-more-lgtm needs-cherry-pick-release-8.0 Should cherry pick this PR to release-8.0 branch. needs-cherry-pick-release-8.1 Should cherry pick this PR to release-8.1 branch. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. translation/doing This PR's assignee is translating this PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants