tencent cloud

PrevNext

Feedback

search by keyword

Recent Pages

Documentation
Documentation

DescribeClusterConfigsHistory

Last updated: 2024-09-12 11:56:31

1. API Description

Domain name for API request: cdwdoris.tencentcloudapi.com.

This API is used to obtain the modification history of cluster configuration files.

A maximum of 20 requests can be initiated per second for this API.

We recommend you to use API Explorer
Try it
API Explorer provides a range of capabilities, including online call, signature authentication, SDK code generation, and API quick search. It enables you to view the request, response, and auto-generated examples.

2. Input Parameters

The following request parameter list only provides API request parameters and some common parameters. For the complete common parameter list, see Common Request Parameters.

Parameter Name Required Type Description
Action Yes String Common Params. The value used for this API: DescribeClusterConfigsHistory.
Version Yes String Common Params. The value used for this API: 2021-12-28.
Region No String Common Params. This parameter is not required for this API.
InstanceId Yes String Cluster ID
Offset Yes Integer Pagination parameters. The first page is 0, and the second page is 10.
Limit Yes Integer Pagination parameters. The pagination step length is 10 by default.
StartTime Yes String Start of the time range for configuration modification history
EndTime Yes String End of the time range for configuration modification history
ConfigFileNames.N No Array of String Configuration file name array to be queried. If it is empty, all historical records will be queried. Currently supported configuration file names are as follows:
apache_hdfs_broker.conf; be.conf; fe.conf; core-site.xml; hdfs-site.xml; odbcinst.ini

3. Output Parameters

Parameter Name Type Description
TotalCount Integer Total number of instances
ClusterConfHistory Array of ClusterConfigsHistory Modification history of the configuration file
RequestId String The unique request ID, generated by the server, will be returned for every request (if the request fails to reach the server for other reasons, the request will not obtain a RequestId). RequestId is required for locating a problem.

4. Example

Example1 test

Input Example

POST / HTTP/1.1
Host: cdwdoris.tencentcloudapi.com
Content-Type: application/json
X-TC-Action: DescribeClusterConfigsHistory
<Common request parameters>

{
    "InstanceId": "abc",
    "ConfigFileNames": [
        "abc"
    ],
    "Offset": 0,
    "Limit": 0,
    "StartTime": "abc",
    "EndTime": "abc"
}

Output Example

{
    "Response": {
        "TotalCount": 0,
        "ClusterConfHistory": [
            {
                "FileName": "abc",
                "NewConfValue": "abc",
                "OldConfValue": "abc",
                "Remark": "abc",
                "ModifyTime": "abc",
                "UserUin": "abc"
            }
        ],
        "RequestId": "abc"
    }
}

5. Developer Resources

SDK

TencentCloud API 3.0 integrates SDKs that support various programming languages to make it easier for you to call APIs.

Command Line Interface

6. Error Code

The following only lists the error codes related to the API business logic. For other error codes, see Common Error Codes.

Error Code Description
InternalError Internal error.
Copyright © 2013-2024 Tencent Cloud. All Rights Reserved.
Privacy PolicyLegalCookie Policy