Compare commits

...

1 Commits

Author SHA1 Message Date
460744bde9 Update content 2023-09-07 12:07:52 +00:00
11 changed files with 392 additions and 310 deletions

File diff suppressed because it is too large Load Diff

View File

@ -5,9 +5,7 @@
Installing Third-Party Software Using Bootstrap Actions Installing Third-Party Software Using Bootstrap Actions
======================================================= =======================================================
This operation applies to MRS 3.\ *x* or earlier clusters. This operation applies to clusters earlier than MRS 3.x.
In MRS 3.\ *x*, bootstrap actions cannot be added during cluster creation.
Prerequisites Prerequisites
------------- -------------

View File

@ -78,11 +78,19 @@ Procedure
7. Run the following command to generate a new certificate file. Then check whether the alarm is automatically cleared one hour later. 7. Run the following command to generate a new certificate file. Then check whether the alarm is automatically cleared one hour later.
**sh geneJKS.sh -f** *sNetty12@* **-g** *cNetty12@* **sh geneJKS.sh -f** *Custom certificate password of the Flume role on the server* **-g** *Custom certificate password of the Flume role on the client*
- If yes, go to :ref:`8 <alm-24010__li57811511185514>`. - If yes, go to :ref:`8 <alm-24010__li57811511185514>`.
- If no, go to :ref:`9 <alm-24010__li593632253716>`. - If no, go to :ref:`9 <alm-24010__li593632253716>`.
.. note::
The custom certificate passwords must meet the following complexity requirements:
- Contain at least four types of uppercase letters, lowercase letters, digits, and special characters.
- Contain 8 to 64 characters.
- Be changed periodically (for example, every three months), and certificates and trust lists are generated again to ensure security.
8. .. _alm-24010__li57811511185514: 8. .. _alm-24010__li57811511185514:
Check whether this alarm is generated again during periodic system check. Check whether this alarm is generated again during periodic system check.

View File

@ -74,11 +74,19 @@ Procedure
Run the following command to generate a new certificate file. Then check whether the alarm is automatically cleared one hour later. Run the following command to generate a new certificate file. Then check whether the alarm is automatically cleared one hour later.
**sh geneJKS.sh -f** *sNetty12@* **-g** *cNetty12@* **sh geneJKS.sh -f** *Custom certificate password of the Flume role on the server* **-g** *Custom certificate password of the Flume role on the client*
- If yes, go to :ref:`9 <alm-24011__li127861713811>`. - If yes, go to :ref:`9 <alm-24011__li127861713811>`.
- If no, go to :ref:`8 <alm-24011__li6673192244411>`. - If no, go to :ref:`8 <alm-24011__li6673192244411>`.
.. note::
The custom certificate passwords must meet the following complexity requirements:
- Contain at least four types of uppercase letters, lowercase letters, digits, and special characters.
- Contain 8 to 64 characters.
- Be changed periodically (for example, every three months), and certificates and trust lists are generated again to ensure security.
8. .. _alm-24011__li6673192244411: 8. .. _alm-24011__li6673192244411:
Log in to the Flume node for which the alarm is generated as user **omm** and repeat :ref:`6 <alm-24011__li1778591515212>` to :ref:`7 <alm-24011__li1599711402218>`. Then, check whether the alarm is automatically cleared one hour later. Log in to the Flume node for which the alarm is generated as user **omm** and repeat :ref:`6 <alm-24011__li1778591515212>` to :ref:`7 <alm-24011__li1599711402218>`. Then, check whether the alarm is automatically cleared one hour later.

View File

@ -75,11 +75,19 @@ Procedure
Run the following command to generate a new certificate file. Then check whether the alarm is automatically cleared one hour later. Run the following command to generate a new certificate file. Then check whether the alarm is automatically cleared one hour later.
**sh geneJKS.sh -f** *sNetty12@* **-g** *cNetty12@* **sh geneJKS.sh -f** *Custom certificate password of the Flume role on the server* **-g** *Custom certificate password of the Flume role on the client*
- If yes, go to :ref:`8 <alm-24012__li1788491915716>`. - If yes, go to :ref:`8 <alm-24012__li1788491915716>`.
- If no, go to :ref:`7 <alm-24012__li172496117507>`. - If no, go to :ref:`7 <alm-24012__li172496117507>`.
.. note::
The custom certificate passwords must meet the following complexity requirements:
- Contain at least four types of uppercase letters, lowercase letters, digits, and special characters.
- Contain 8 to 64 characters.
- Be changed periodically (for example, every three months), and certificates and trust lists are generated again to ensure security.
7. .. _alm-24012__li172496117507: 7. .. _alm-24012__li172496117507:
Log in to the Flume node for which the alarm is generated as user **omm** and repeat :ref:`5 <alm-24012__li161213411093>` to :ref:`6 <alm-24012__li084616591915>`. Then, check whether the alarm is automatically cleared one hour later. Log in to the Flume node for which the alarm is generated as user **omm** and repeat :ref:`5 <alm-24012__li161213411093>` to :ref:`6 <alm-24012__li084616591915>`. Then, check whether the alarm is automatically cleared one hour later.

View File

@ -78,11 +78,19 @@ Procedure
7. Run the following command to generate a new certificate file. Then check whether the alarm is automatically cleared one hour later. 7. Run the following command to generate a new certificate file. Then check whether the alarm is automatically cleared one hour later.
**sh geneJKS.sh -m** *sKitty12@* **-n** *cKitty12@* **sh geneJKS.sh -m** *Custom password of the MonitorServer certificate on the server* **-n** *Custom password of the MonitorServer certificate on the client*
- If yes, go to :ref:`8 <alm-24013__li57811511185514>`. - If yes, go to :ref:`8 <alm-24013__li57811511185514>`.
- If no, go to :ref:`9 <alm-24013__li593632253716>`. - If no, go to :ref:`9 <alm-24013__li593632253716>`.
.. note::
The custom certificate passwords must meet the following complexity requirements:
- Contain at least four types of uppercase letters, lowercase letters, digits, and special characters.
- Contain 8 to 64 characters.
- Be changed periodically (for example, every three months), and certificates and trust lists are generated again to ensure security.
8. .. _alm-24013__li57811511185514: 8. .. _alm-24013__li57811511185514:
Check whether this alarm is generated again during periodic system check. Check whether this alarm is generated again during periodic system check.

View File

@ -74,11 +74,19 @@ Procedure
Run the following command to generate a new certificate file. Then check whether the alarm is automatically cleared one hour later. Run the following command to generate a new certificate file. Then check whether the alarm is automatically cleared one hour later.
**sh geneJKS.sh -m** *sKitty12@* **-n** *cKitty12@* **sh geneJKS.sh -m** *Custom password of the MonitorServer certificate on the server* **-n** *Custom password of the MonitorServer certificate on the client*
- If yes, go to :ref:`9 <alm-24014__li127861713811>`. - If yes, go to :ref:`9 <alm-24014__li127861713811>`.
- If no, go to :ref:`8 <alm-24014__li6673192244411>`. - If no, go to :ref:`8 <alm-24014__li6673192244411>`.
.. note::
The custom certificate passwords must meet the following complexity requirements:
- Contain at least four types of uppercase letters, lowercase letters, digits, and special characters.
- Contain 8 to 64 characters.
- Be changed periodically (for example, every three months), and certificates and trust lists are generated again to ensure security.
8. .. _alm-24014__li6673192244411: 8. .. _alm-24014__li6673192244411:
Log in to the Flume node for which the alarm is generated as user **omm** and repeat :ref:`6 <alm-24014__li368813032118>` to :ref:`7 <alm-24014__li153512414216>`. Then, check whether the alarm is automatically cleared one hour later. Log in to the Flume node for which the alarm is generated as user **omm** and repeat :ref:`6 <alm-24014__li368813032118>` to :ref:`7 <alm-24014__li153512414216>`. Then, check whether the alarm is automatically cleared one hour later.

View File

@ -75,11 +75,19 @@ Procedure
Run the following command to generate a new certificate file. Then check whether the alarm is automatically cleared one hour later. Run the following command to generate a new certificate file. Then check whether the alarm is automatically cleared one hour later.
**sh geneJKS.sh -m** *sKitty12@* **-n** *cKitty12@* **sh geneJKS.sh -m** *Custom password of the MonitorServer certificate on the server* **-n** *Custom password of the MonitorServer certificate on the client*
- If yes, go to :ref:`8 <alm-24015__li1788491915716>`. - If yes, go to :ref:`8 <alm-24015__li1788491915716>`.
- If no, go to :ref:`7 <alm-24015__li172496117507>`. - If no, go to :ref:`7 <alm-24015__li172496117507>`.
.. note::
The custom certificate passwords must meet the following complexity requirements:
- Contain at least four types of uppercase letters, lowercase letters, digits, and special characters.
- Contain 8 to 64 characters.
- Be changed periodically (for example, every three months), and certificates and trust lists are generated again to ensure security.
7. .. _alm-24015__li172496117507: 7. .. _alm-24015__li172496117507:
Log in to the Flume node for which the alarm is generated as user **omm** and repeat :ref:`5 <alm-24015__li160343112815>` to :ref:`6 <alm-24015__li68486146283>`. Then, check whether the alarm is automatically cleared one hour later. Log in to the Flume node for which the alarm is generated as user **omm** and repeat :ref:`5 <alm-24015__li160343112815>` to :ref:`6 <alm-24015__li68486146283>`. Then, check whether the alarm is automatically cleared one hour later.

View File

@ -50,6 +50,8 @@ System Users
| Node OS user | ommdba | Random password | User that creates the system database. This user is an OS user generated on the management node and does not require a unified password. This account cannot be used for remote login. | For details, see :ref:`Changing the Password for an OS User <admin_guide_000251>`. | | Node OS user | ommdba | Random password | User that creates the system database. This user is an OS user generated on the management node and does not require a unified password. This account cannot be used for remote login. | For details, see :ref:`Changing the Password for an OS User <admin_guide_000251>`. |
+----------------------+-------------+-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------+ +----------------------+-------------+-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------+
| | omm | Bigdata123@ | Internal running user of the system. This user is an OS user generated on all nodes and does not require a unified password. | | | | omm | Bigdata123@ | Internal running user of the system. This user is an OS user generated on all nodes and does not require a unified password. | |
| | | | | |
| | | | In MRS 3.2.0-LTS.2 or later, the password of user **omm** is randomly generated. | |
+----------------------+-------------+-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------+ +----------------------+-------------+-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------+
Internal System Users Internal System Users

View File

@ -7,7 +7,7 @@ Adding a Bootstrap Action
Add a bootstrap action. Add a bootstrap action.
This operation applies to MRS 3.\ *x* or earlier clusters. This operation applies to clusters earlier than MRS 3.\ *x*.
Procedure Procedure
--------- ---------