logo
Alauda Streaming Service for Kafka
logo
Alauda Streaming Service for Kafka
Navigation
Introduction
Release Notes
Lifecycle Policy
Install
Upgrade
Architecture

Guides

Create Instance
Delete Instance
User Management
Topic Management
Parameter Configuration
Update Scheduling Configuration
Monitoring and Alerts
Log
Restart Instance
Start and Stop Instance

HowTo

Specification Changes
Choosing Connection Address and Configuring Connection Method
Patch Version Upgrade
Client File Configuration
Permissions

API Reference

Kubernetes APIs

Kafka APIs

RdsKafka
RdsTopic
RdsKafkaUser
📝 Edit this page on GitHub
Previous PageParameter Configuration
Next PageMonitoring and Alerts

#Update Scheduling Configuration

When the node taints change, it supports adding, modifying, or deleting Pod tolerations. Updating the scheduling configuration will not affect the normal service availability.

#TOC

#Notes

  • Pod migration is not supported. After changing Pod tolerations, the selected nodes must include the nodes that existed before the update.

  • If you have configured node labels, the number of nodes matching Pod tolerations and node taints must be greater than or equal to the replica count. The updated available nodes must either remain the same as the original available nodes or add new nodes on top of the original available nodes for the scheduling configuration to update successfully.

#Procedure

Web Console
  1. In the left navigation bar, click Kafka.

  2. Click namespace name.

  3. Click instance name.

  4. Click Actions > Update Scheduling Configuration in the upper right corner.

  5. Modify the configuration as needed.

  6. Click Update.