You can adjust the message retention period, maximum message size, consumer offset retention period, and SSL certificate key size to meet your business requirements.
Configurations
ApsaraMQ for Kafka allows you to modify settings such as the message retention period, maximum message size, consumer offset retention period, and SSL certificate key size. Configure these settings as needed.
The time required to modify message configurations depends on the instance specification. For instances of alikafka.hr.30xlarge or alikafka.hw.30xlarge and lower, the process takes about 30 minutes. For instances of alikafka.hr.60xlarge or alikafka.hw.60xlarge and higher, it takes more than 1 hour. In general, the larger the instance specification, the longer the process takes.
|
Parameter |
Description |
|
Message Retention Period |
The maximum duration a message is retained, assuming sufficient disk space.
|
|
Maximum Message Size |
The maximum size of a message that ApsaraMQ for Kafka can send or receive.
|
|
Consumer Offset Retention Period |
The maximum retention period for consumer offsets. The countdown starts when a consumer offset is committed. The system deletes consumer offsets that exceed this period. Each time you commit a consumer offset to a topic partition, the retention countdown resets and starts from 0. The default retention period is 7 days (10,080 minutes). Valid values: 1,440 to 43,200 minutes. Note
If a consumer group has at least one active consumer thread, its consumer offsets will not be deleted, even if the Consumer Offset Retention Period has expired. For more information, see Why are expired consumer offsets retained?. |
|
SSL Certificate Key Size (Bits) |
The key size of the SSL certificate for the instance's public network endpoint. You can upgrade the key size from 1,024 to 4,096 bits, but we do not recommend downgrading from 4,096 to 1,024 bits. To perform an upgrade, you must first upgrade the certificate key size on your client and then restart the client. For detailed instructions, see Update the SSL certificate algorithm. |
Procedure
Log on to the ApsaraMQ for Kafka console. In the Resource Distribution section of the Overview page, select the region where the ApsaraMQ for Kafka instance that you want to manage resides.
On the Instances page, click the name of the instance that you want to manage.
-
On the Instance Details page, find the Configuration Information section. Click Edit next to message retention period, maximum message size, consumer offset retention period, SSL certificate key size, or secondary availability zone to modify the corresponding parameter.
-
In the Risks of Configuration Modification dialog box, read and acknowledge the risks, and then click OK.
Be aware of the following risks: This operation triggers a rolling restart of the cluster, which can cause brief service interruptions. Clients without an automatic reconnection mechanism may be disconnected and fail to reconnect. After the update, you must verify that your applications are functioning correctly.