Updated on 2022-09-19 GMT+08:00

Creating a Hot Key Analysis Task

Function

This API is used to create a hot key analysis task. Redis 3.0 does not support hot key analysis.

To perform hot key analysis, the instance's maxmemory-policy parameter must be set to allkeys-lfu or volatile-lfu.

URI

POST /v2/{project_id}/instances/{instance_id}/hotkey-task

Table 1 Path Parameters

Parameter

Mandatory

Type

Description

project_id

Yes

String

Project ID.

instance_id

Yes

String

Instance ID.

Request Parameters

None

Response Parameters

Status code: 200

Table 2 Response body parameters

Parameter

Type

Description

id

String

Hot key analysis record ID.

instance_id

String

Instance ID.

status

String

Analysis task status.

Enumeration values:

  • waiting
  • running
  • success
  • failed

scan_type

String

Analysis mode.

Enumeration values:

  • manual
  • auto

created_at

String

Time when an analysis task is created. The format is "2020-06-15T02:21:18.669Z".

started_at

String

Time when an analysis task started. The format is "2020-06-15T02:21:18.669Z". (The value is null and is not returned when the analysis task is being created.)

finished_at

String

Time when an analysis task ended. The format is "2020-06-15T02:21:18.669Z". (The value is null and is not returned when the analysis task is being created.)

num

Integer

Number of hot keys.

keys

Array of HotkeysBody objects

Hot key record. (The value is null and is not returned when the analysis task is being created.)

Table 3 HotkeysBody

Parameter

Type

Description

name

String

Key name.

type

String

Key type.

Enumeration values:

  • string
  • list
  • set
  • zset
  • hash

shard

String

Shard where the hot key is located. This parameter is supported only when the instance type is cluster. The format is ip:port.

db

Integer

Database where the hot key is located.

size

Integer

Size of the key value.

unit

String

Unit of the key size. When the key type is string, the unit is byte. When the key type is list, set, zset, or hash, the unit is count.

freq

Integer

Access frequency of a key within a specific period of time.

The value is the logarithmic access frequency counter. The maximum value is 255, which indicates 1 million access requests. After the frequency reaches 255, the value will no longer increase even if access requests continue to increase. The value will decrease by 1 for every minute during which the key is not accessed.

Status code: 400

Table 4 Response body parameters

Parameter

Type

Description

error_msg

String

Error message.

Maximum: 1024

error_code

String

Error code.

Maximum: 9

error_ext_msg

String

Extended error information. This parameter is not used currently and is set to null.

Maximum: 1024

Status code: 401

Table 5 Response body parameters

Parameter

Type

Description

error_msg

String

Error message.

Maximum: 1024

error_code

String

Error code.

Maximum: 9

error_ext_msg

String

Extended error information. This parameter is not used currently and is set to null.

Maximum: 1024

Status code: 403

Table 6 Response body parameters

Parameter

Type

Description

error_msg

String

Error message.

Maximum: 1024

error_code

String

Error code.

Maximum: 9

error_ext_msg

String

Extended error information. This parameter is not used currently and is set to null.

Maximum: 1024

Status code: 404

Table 7 Response body parameters

Parameter

Type

Description

error_msg

String

Error message.

Maximum: 1024

error_code

String

Error code.

Maximum: 9

error_ext_msg

String

Extended error information. This parameter is not used currently and is set to null.

Maximum: 1024

Status code: 500

Table 8 Response body parameters

Parameter

Type

Description

error_msg

String

Error message.

Maximum: 1024

error_code

String

Error code.

Maximum: 9

error_ext_msg

String

Extended error information. This parameter is not used currently and is set to null.

Maximum: 1024

Example Requests

POST https://dcs.cn-south-1.myhuaweicloud.com/v2/a4d31cb6-3d72-4fdc-8ec9-6e3a41e47f71/instances/5560df16-cebf-4473-95c4-d1b573c16e79/hotkey-task

Example Responses

Status code: 200

Hot key analysis task created successfully.

{
  "id" : "aa735b6f-3d70-44e3-9771-66c6fae7459a",
  "instance_id" : "5560df16-cebf-4473-95c4-d1b573c16e79",
  "status" : "waiting",
  "scan_type" : "manual",
  "created_at" : "2020-06-15T02:21:18.669Z",
  "num" : 0
}

Status code: 400

Invalid request.

{
  "error_code" : "DCS.4922",
  "error_msg" : "Does not support hotkey analyze."
}

Status Codes

Status Code

Description

200

Hot key analysis task created successfully.

400

Invalid request.

401

Invalid authentication information.

403

The request is rejected.

404

The requested resource is not found.

500

Internal service error.

Error Codes

See Error Codes.