Help Center > > User Guide> Configuring Clusters> Bootstrap Actions> Adding a Bootstrap Action

Adding a Bootstrap Action

Updated at: Apr 28, 2020 GMT+08:00

Adding a Bootstrap Action When Creating a Cluster

  1. Log in to the MRS management console.
  2. Click Buy Cluster. The Buy Cluster page is displayed.
  3. On the Advanced Settings tab page, select Configure. The Bootstrap Action tab page is displayed.
  4. On the Bootstrap Action tab page, click Add. The page is displayed, as shown in the following figure.

    Table 1 Parameters




    Name of a bootstrap action script

    The value can contain only digits, letters, spaces, hyphens (-), and underscores (_) and cannot start with a space.

    The value can contain 1 to 64 characters.


    A name must be unique in the same cluster. You can set the same name for different clusters.

    Script Path

    Script path. The value can be an OBS bucket path or a local VM path.

    • An OBS bucket path must start with s3a:// and end with .sh.
    • A local VM path must start with a slash (/) and end with .sh. For example, the path of the example script for installing Zeppelin is as follows: /opt/bootstrap/zeppelin/

    Execution Node

    Select a type of the node where the bootstrap action script is executed.

    • If you select Master, you can choose whether to run the script only on the active Master nodes by enabling or disabling the switch .
    • If you enable it, the script runs only on the active Master nodes. If you disable it, the script runs on all Master nodes. This switch is disabled by default.


    Bootstrap action script parameters

    Execution Time

    Select the time when the bootstrap action script is executed. Currently, the following two options are available: Before component start and After component start

    Action upon Failure

    Whether to continue to execute subsequent scripts and create a cluster after the script fails to be executed.

    You are advised to set this parameter to Continue in the debugging phase so that the cluster can continue to be installed and started no matter whether the bootstrap action is successful.

  5. Click OK.

    After the bootstrap action is successfully added, you can edit or delete it in the Operation column.

Adding an Automation Script on the Auto Scaling Page

  1. Log in to the MRS management console.
  2. Choose Clusters > Active Clusters, select a running cluster, and click its name to switch to the cluster details page.
  3. On the Nodes tab page, click Auto Scaling in the Operation column of the Task node group. The Auto Scaling page is displayed.
  4. Configure a resource plan.

    You can configure the resource plan to adjust the number of nodes, which affects the actual price. Therefore, exercise caution when performing this operation.

    Configuration procedure:

    1. On the Auto Scaling page, enable Auto Scaling.
      Figure 1 Auto scaling page
    2. Set Default Range to 2-2 for Node Range. This indicates that the number of Task nodes is fixed to 2 beyond the time range specified in the resource plan.
    3. Click Configure Node Range in a Specified Time Range under Default Range.
    4. Configure Time Range to 07:00-13:00, and Node Range to 5-5. This indicates that the number of Task nodes is fixed to 5 in the specified time range. For details about the parameters, see Table 2.

      You can click Configure Node Range in a Specified Time Range to configure multiple resource plans.

  5. (Optional) Configure an automation script.

    1. In Automation Script of Advanced Settings, click Add. The Automation Script page is displayed.
    Figure 2 Automation script
    1. Set the following parameters: Name, Script Path, Execution Node Type, Parameter, Execution Time, and Action upon Failure. For details about the parameters, see Table 3.
    2. Click OK to save the automation script configurations.

  6. Select I agree to authorize MRS to scale out or in nodes based on the above policy.
  7. Click OK.

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?

Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel