Distributed Message Service for RocketMQ
Distributed Message Service for RocketMQ
- What's New
- Function Overview
- Product Bulletin
- Service Overview
- Getting Started
-
User Guide
- Process of Using RocketMQ
- Creating a User and Granting DMS for RocketMQ Permissions
- Buying a RocketMQ Instance
- Configuring a Topic
- Accessing an Instance
- Managing Messages
- Managing Consumer Groups
-
Managing Instances
- Viewing and Modifying Basic Information of a RocketMQ Instance
- Viewing Background Tasks of a RocketMQ Instance
- Configuring Tags for a RocketMQ Instance
- Exporting RocketMQ Instances
- Diagnosing a RocketMQ Instance
- Restarting Brokers of a RocketMQ Instance
- Deleting a RocketMQ Instance
- Configuring SSL of a RocketMQ Instance
- Modifying RocketMQ Specifications
- Migrating Metadata
- Viewing Monitoring Metrics and Configuring Alarms
- Viewing RocketMQ Audit Logs
- Best Practices
- Developer Guide
- API Reference
- SDK Reference
- FAQs
- Videos
On this page
Help Center/
Distributed Message Service for RocketMQ/
API Reference/
APIs V2 (Recommended)/
Consumer Group Management/
Deleting a Consumer Group
Deleting a Consumer Group
Updated on 2022-09-14 GMT+08:00
Function
This API is used to delete a specified consumer group.
URI
DELETE /v2/{project_id}/instances/{instance_id}/groups/{group}
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
project_id |
Yes |
String |
Project ID. Minimum: 32 Maximum: 32 |
instance_id |
Yes |
String |
Instance ID. |
group |
Yes |
String |
Consumer group name. |
Request Parameters
None
Response Parameters
None
Example Requests
Deleting a consumer group
DELETE https://{endpoint}/v2/{project_id}/instances/{instance_id}/groups/{group}
Example Responses
None
Status Codes
Status Code |
Description |
---|---|
204 |
The operation is successful. |
Error Codes
See Error Codes.
Parent topic: Consumer Group Management
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.