Updating the BLU Configuration

Scenario

Manually adjust the configuration sets used by a BLU based on service requirements when a group has multiple configuration sets. The new configuration set can be selected from the existing ones of the current group or reuploaded. After the configuration set is updated, the BLU needs to be restarted for the update to take effect. You can roll-restart all BLU instances that are running properly in three batches to prevent service interruption caused by one restart.

Procedure

1. Log in to FusionInsight Manager.
2. Choose Cluster > Services > Containers, and click the Business Manager tab.
3. In the list on the left, click the group to which the target BLU belongs.
4. In the list on the right, locate the row that contains the target BLU and click in the Operation column. In the dialog box that is displayed, click OK.
5. (Optional) Enter the description in the Description text box. The description contains a maximum of 120 characters.
6. Adjust the configuration set.
   • To add a configuration set for the BLU, click add a configuration set. In the dialog box that is displayed, click OK. The Add a group configuration set page is displayed. For details about how to add a configuration set, see Creating a Group.
   • If there are two or more configuration sets and the priority of the configuration sets needs to be configured, select the configuration sets and click Set Priority. In the dialog box that is displayed, click or in the Set Priority column to adjust the priority. Then, click OK.
     

     The BLU package can also integrate configuration set files of the BLU. If different configuration set files contain same configuration files, the priorities of the configuration files in descending order are as follows: configuration files added through Custom Configuration, configuration files of a group, and configuration file integrated in a BLU package. You can select multiple configuration files of a group and specify their priorities. The file with a higher priority overwrites the file with a lower priority.

     The default size limit for a single BLU package and configuration set is 300 MB.

   • If the BLU requires configuration files that are not in the current group configuration set due to service requirements, you can select Custom Configuration to activate the Select File button and click the button to add configuration files.
   • Determine whether to select Merge With the Previous Configuration based on service requirements. If this parameter is selected, incremental update is performed. You can choose to update some files of the configuration set. The files will be merged in the background.

7. In the Restart Strategy area, select a restart policy based on service requirements.
   • Redeploy immediately
   • Do not redeploy
     

     If you select Do not Redeploy, only the updated configuration is delivered to the BLU run directory. If the BLU does not support dynamic configuration loading, do not select this option. Otherwise, the BLU cannot detect configuration changes.

   • Rolling redeploy
     

     • If you select Rolling Redeploy, you need to configure the waiting time for restarting each batch of BLU instances. In the Timeout of waiting for each turn BLU instances to complete configuration update (min) text box, enter the timeout interval for each BLU instance to complete configuration update.

       The default value is 2 minutes. The value ranges from 2 to 5.

     • After the task is submitted, you can view the restart task information on Task Management of the Business Manager tab page. If an exception occurs during task execution, you can roll back, ignore, terminate, or retry the task.

8. Click OK.