Updated on 2024-11-29 GMT+08:00

Updating an RTDService Tenant

Scenario

An RTDService tenant needs to be updated in the following scenarios:

  • Tenant basic information change
  • Farmer cluster configuration change
  • MOTService configuration change
  • Redis configuration change
  • Kafka configuration change

The RTD tenant records information about RTDservice, MOTService, Redis service (optional), and Kafka service (optional). If the configurations of theses services change, the RTD tenant needs to be updated.

The following content describes how to update a tenant.

Procedure

Update the tenant on the RTD web UI.

  1. Log in to the RTD web UI. For details, see Accessing the RTDService Web UI.
  2. Choose System > Tenant Management.
  3. In the tenant list, click Modify next to the tenant name, modify configurations of Farmer, MOTService, Redis, and Kafka clusters as required, and click OK to save the configurations.
  4. (Optional) Synchronize RTDExecutor.

    In the tenant list, click Synchronize RTDExecutor next to the tenant name, select the cluster you want to synchronize, and click OK. Wait until the synchronization is successful.

Update through an API.

  1. Record the IP address for logging in to FusionInsight Manager of the cluster where RTDService is deployed.
  2. Log in to https://omsip:21820/rtdservice/v1/tenants/tenant ID.

    Send the JSON body with PUT method.

    {
        "tenantId": "Tenant ID",
        "name": "mot_test1",
        "dbType": 1,
        "modifiedTime": null,
        "modifiedUser": null,
        "description": null,
        "createdTime": "2022-09-09 11:26:29.58",
        "createdUser": null,
        "clusterConfig": {
            "fiFarmer2ManagerUser": null,
            "fiFarmer1ManagerOmPort": 20009,
            "fiFarmer2ManagerIp": null,
            "fiFarmer1ContainersGroupName": "RTD",
            "fiFarmer1ManagerPassword": "password",
            "fiFarmer1ManagerUser": "admin",
            "fiFarmer2ManagerPassword": null,
            "fiFarmer2ContainersGroupName": null,
            "fiFarmer2ManagerPort": 0,
            "fiFarmer1ManagerIp": "192.168.64.12",
            "fiFarmer1ManagerPort": 28443,
            "fiFarmer2ManagerOmPort": 0
        },
        "rtdDbConfig": [
            {
                "rtddbGroupId": "1",
                "rtddbGroupName": "mot_group1",
                "dbAuthMode": 0,
                "rtddbGroupInstallMode": 1,
                "dbCallProcedureTimeout": 100000,
                "db1ConnectionUser": "dttest",
                "db1ConnectionPassword": "password",
                "db1ConnectionIp": "192.168.64.51",
                "db1ConnectionPort": 20105,
                "db1DataBaseName": "db_tpcc",
                "db1SSlEnable": false
            }
        ],
        "redisConfig": [
            {
                "redisClusterId": "1234",
                "redisClusterName": "redis1",
                "redisConnectionUrls": "192.168.64.12:22400,192.168.64.4:22400,192.168.64.95:22400",
                "redisClusterMaxTotal": 20,
                "redisClusterTimeout": 2000,
                "redisClusterMode": 0,
                "redisClusterSSLEnabled": false,
                "redisClusterUsername": "",
                "redisClusterPassword": "",
                "redisClusterKrbConf": ""
            }
        ],
        "kafkaConfig": {
            "kafka1ConnectionUrls": "192.168.64.12:21005,192.168.64.4:21005,192.168.64.95:21005",
            "kafka1ClusterMode": 0,
            "kafka1ClusterSSLEnabled": false,
            "kafka1ClusterUsername": "",
            "kafka1ClusterPassword": "",
            "kafka1ClusterKrbConf": "",
            "kafka2ConnectionUrls": "192.168.64.13:21005,192.168.64.5:21005,192.168.64.96:21005",
            "kafka2ClusterMode": 0,
            "kafka2ClusterSSLEnabled": false,
            "kafka2ClusterUsername": "",
            "kafka2ClusterPassword": "",
            "kafka2ClusterKrbConf": ""
        }
    }

  3. If Status 200 OK is returned, the update is successful.
  4. After the tenant is updated, synchronize the tenant configuration to the RTDExecutor BLU. For details, see Synchronizing Tenant Configurations to the RTDExecutor BLU.
  5. Check the BLU health status and service status.

Synchronizing Tenant Configurations to the RTDExecutor BLU

After the tenant configuration (including configurations of Farmer, MOTService, Redis, and Kafka clusters) is updated, you can synchronize the configuration to RTDExecutor BLU on the RTD web UI.

  1. Log in to the RTD web UI. For details, see Accessing the RTDService Web UI.
  2. Choose System > Tenant Management.
  3. In the tenant list, click Synchronize RTDExecutor next to the tenant name, select the cluster you want to synchronize, and click confirm.
  4. Wait until the system synchronization is successful.