Skip to content

Update notices to notes in O&M documentation #357

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.

Sign up for GitHub

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

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

Update notices to notes in O&M documentation #357

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions ...manual/quick_starts/en-US/chapter_05_operation_and_maintenance/02_o_m_by_obd.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,7 +112,7 @@ The following describes the general O&M procedure in OBD through an example of m

When you increase resource parameter values, make sure that the new values do not exceed the range of the remaining resources on servers. When you decrease resource parameter values, make sure that the new values are not smaller than the sizes of resources that have been allocated to or occupied by tenants. For more information about the relationships among resource parameters, see the **Common resource parameters of OceanBase Database and their calculation methods** section in **2.1 Deploy OceanBase database - Preparations before deployment**.

> **Notice**
> **Note**
>
> You cannot decrease the value of the `datafile_size` parameter.

Expand Down Expand Up @@ -260,7 +260,7 @@ Take note of the following considerations:

* The status of a deployed cluster is `running` in the `obd cluster list` command output only if all components in the cluster have been restarted. If any component fails to be restarted, subsequent components will not be restarted.

> **Notice**
> **Note**
>
> The status of the deployed cluster returned in the `obd cluster list` command output is not updated in real time. When a server restarts, the service component on the server may become abnormal while the status of the cluster is still displayed as `running`. Therefore, we recommend that after a server restarts, you run the `obd cluster display` command to verify whether all components are normal.

Expand Down