Deprecated config properties

redpanda-data · Jul 11, 2024 · 614f7cb · 614f7cb
1 parent eac1f82
commit 614f7cb
Show file tree

Hide file tree

Showing 2 changed files with 20 additions and 122 deletions.
diff --git a/modules/reference/pages/properties/cluster-properties.adoc b/modules/reference/pages/properties/cluster-properties.adoc
@@ -1580,30 +1580,6 @@ Time between cluster join retries in milliseconds.
 
 ---
 
-=== kafka_admin_topic_api_rate
-
-Target quota rate for partition mutations per <<default_window_sec,`default_window_sec`>>. If `null`, the property is disabled, and no quota rate is applied.
-
-*Unit*: partition mutations per `default_window_second`
-
-*Related properties*:
-
-* <<default_window_sec,`default_window_sec`>>
-
-*Requires restart:* No
-
-*Optional:* No
-
-*Visibility:* `user`
-
-*Type:* integer
-
-*Accepted values:* [`0`, `4294967295`]
-
-*Default:* `null`
-
----
-
 === kafka_batch_max_bytes
 
 Maximum size of a batch processed by the server. If the batch is compressed, the limit applies to the compressed batch size.
@@ -1622,58 +1598,6 @@ Maximum size of a batch processed by the server. If the batch is compressed, the
 
 ---
 
-=== kafka_client_group_byte_rate_quota
-
-A map specifying the produce-rate quota per client group. The configurable fields:
-
-Example: `([{'group_name': 'first_group','clients_prefix': 'group_1','quota': 10240}])`
-
-*Related topics*:
-
-* xref:manage:cluster-maintenance/manage-throughput.adoc#client-group-throughput-limits[Client group throughput limits]
-
-*Requires restart:* No
-
-*Optional:* Yes
-
-*Visibility:* `user`
-
-*Accepted Values:*
-
-* `group_name`: Name of a client group
-* `clients_prefix`: Prefix to prepend to the name of each client belonging to the group specified by `group_name`
-* `quota`: Produce-rate quota of each client in bytes per second
-
-*Default:* `null`
-
----
-
-=== kafka_client_group_fetch_byte_rate_quota
-
-A map specifying the fetch-rate quota per client group. The configurable fields:
-
-Example: `([{'group_name': 'first_group','clients_prefix': 'group_1','quota': 10240}])`
-
-*Related topics*:
-
-* xref:manage:cluster-maintenance/manage-throughput.adoc#client-group-throughput-limits[Client group throughput limits]
-
-*Requires restart:* No
-
-*Optional:* Yes
-
-*Visibility:* `user`
-
-*Accepted Values:*
-
-* `group_name`: Name of a client group
-* `clients_prefix`: Prefix to prepend to the name of each client belonging to the group specified by `group_name`
-* `quota`: Produce-rate quota of each client in bytes per second
-
-*Default:* `null`
-
----
-
 === kafka_connection_rate_limit
 
 Maximum connections per second for one core. If `null` (the default), then the number of connections per second is unlimited.
@@ -5142,52 +5066,6 @@ List of superuser usernames.
 
 ---
 
-=== target_fetch_quota_byte_rate
-
-Target fetch-size quota byte rate. If `null`, the property is disabled, and no quota byte rate is applied.
-
-*Unit*: bytes per second
-
-*Requires restart:* No
-
-*Optional:* No
-
-*Visibility:* `user`
-
-*Type:* integer
-
-*Accepted values:* [`0`, `4294967295`]
-
-*Default:* `null`
-
----
-
-=== target_quota_byte_rate
-
-Target quota byte rate.
-
-The `target_quota_byte_rate` property applies to a producer client that isn't a member of a client group configured by <<kafka_client_group_byte_rate_quota,`kafka_client_group_byte_rate_quota`>>. It sets the maximum throughput quota of a client sending to a Redpanda broker node.
-
-*Related topics*:
-
-* xref:manage:cluster-maintenance/manage-throughput.adoc#client-throughput-limits[Client throughput limits]
-
-*Unit*: bytes per second
-
-*Requires restart:* No
-
-*Optional:* Yes
-
-*Visibility:* `user`
-
-*Type:* integer
-
-*Accepted values:* [`0`, `4294967295`]
-
-*Default:* `2147483648`
-
----
-
 === tm_sync_timeout_ms
 
 Transaction manager's synchronization timeout. Maximum time to wait for internal state machine to catch up before rejecting a request.

diff --git a/modules/upgrade/pages/deprecated/index.adoc b/modules/upgrade/pages/deprecated/index.adoc
@@ -9,6 +9,16 @@ This index helps you to identify deprecated features in Redpanda releases and pl
 |===
 | Deprecated in  | Feature | Details
 
+| 24.2.1
+a| Client throughput quota cluster configuration
+
+- `kafka_client_group_byte_rate_quota`
+- `kafka_client_group_fetch_byte_rate_quota`
+- `target_quota_byte_rate`
+- `target_fetch_quota_byte_rate`
+- `kafka_admin_topic_api_rate`
+| xref:manage:cluster-maintenance/manage-throughput.adoc#client-throughput-limits[Client throughput limits] are now Kafka API-based and should be managed using `rpk cluster quotas`.
+
 | 23.3.2
 | `space_management_enable_override`
 | This property was a workaround in older version of Redpanda. It is no longer required and the property is ignored.
@@ -189,6 +199,12 @@ This is an exhaustive list of all the deprecated properties.
 
 - id_allocator_replication
 
+- kafka_admin_topic_api_rate
+
+- kafka_client_group_byte_rate_quota
+
+- kafka_client_group_fetch_byte_rate_quota
+
 - max_version
 
 - min_version
@@ -203,6 +219,10 @@ This is an exhaustive list of all the deprecated properties.
 
 - seq_table_min_size
 
+- target_fetch_quota_byte_rate
+
+- target_quota_byte_rate
+
 - tm_violation_recovery_policy
 
 - transaction_coordinator_replication