Skip to content

deployment: clarify description about using the same user and UID/GID (#22491)#22507

Merged
ti-chi-bot[bot] merged 7 commits intopingcap:release-8.5from
ti-chi-bot:cherry-pick-22491-to-release-8.5
Feb 27, 2026
Merged

deployment: clarify description about using the same user and UID/GID (#22491)#22507
ti-chi-bot[bot] merged 7 commits intopingcap:release-8.5from
ti-chi-bot:cherry-pick-22491-to-release-8.5

Conversation

@ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #22491

First-time contributors' checklist

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)
  • v9.0 (TiDB 9.0 versions)
  • v8.5 (TiDB 8.5 versions)
  • v8.1 (TiDB 8.1 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)

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

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

@ti-chi-bot ti-chi-bot added lgtm needs-1-more-lgtm Indicates a PR needs 1 more LGTM. ONCALL Relates to documentation oncall. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. type/cherry-pick-for-release-8.5 This PR is cherry-picked to release-8.5 from a source PR. labels Feb 27, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the deployment documentation by providing crucial clarifications on user management. It specifically addresses scenarios where user consistency, including UID and GID, is vital across nodes, such as when using Backup & Restore (BR) or network storage like NFS, to prevent potential permission errors. The changes aim to improve clarity and guide users toward more robust deployment configurations.

Highlights

  • User Consistency Clarification: Clarified documentation regarding the importance of user consistency, including UID and GID, across nodes for TiDB deployments.
  • Backup & Restore (BR) Operations: Emphasized the strong recommendation to perform all BR and TiDB-related operations with the same user to avoid permission issues.
  • Network Storage (NFS) Considerations: Highlighted that for network storage like NFS, users must have the same UID and GID on all nodes to ensure correct file access permissions.
  • User Creation Command Update: Modified the useradd command example to explicitly create a home directory for the tidb user using -m -d /home/tidb.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • check-before-deployment.md
    • Updated the introductory paragraph for SSH mutual trust configuration.
    • Added a new section detailing scenarios where user consistency (same user, UID/GID) is recommended or required, specifically for BR and NFS.
    • Modified the useradd command to include -m -d /home/tidb for explicit home directory creation.
Activity
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request clarifies the description for using the same user and UID/GID during deployment, which is a valuable improvement for documentation clarity. The added details on scenarios requiring user consistency, like Backup & Restore and NFS usage, are particularly helpful. I have one minor suggestion to align the wording more closely with the repository's style guide.

@hfxsd
Copy link
Collaborator

hfxsd commented Feb 27, 2026

/approve

@ti-chi-bot
Copy link

ti-chi-bot bot commented Feb 27, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hfxsd

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

The pull request process is described here

Details 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 the approved label Feb 27, 2026
@ti-chi-bot ti-chi-bot bot merged commit 2f15c4a into pingcap:release-8.5 Feb 27, 2026
11 checks passed
@ti-chi-bot ti-chi-bot bot deleted the cherry-pick-22491-to-release-8.5 branch February 27, 2026 07:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved lgtm needs-1-more-lgtm Indicates a PR needs 1 more LGTM. ONCALL Relates to documentation oncall. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. type/cherry-pick-for-release-8.5 This PR is cherry-picked to release-8.5 from a source PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants