이 페이지는 현재 영어 만 지원하며보고있는 언어를 준비 중입니다.
关闭
TDMQ for CKafka
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Billing Overview
- Getting Started
- Obtaining Access Permission
- VPC Access
- Step 4. Send/Receive Messages
- Access via Public Domain Name
- Step 5. Send/Receive Messages
- Operation Guide
- Instance Management
- Topic Management
- Instance Topic
- Elastic Topic
- Consumer Group
- Monitoring and Alarms
- Smart Ops
- Permission Management
- Tag Management
- Migration to Cloud
- CKafka Connector
- Task Management
- Creating Data Access Task
- Creating Data Distribution Task
- Simple Data Processing
- Practical Tutorial
- Practical Tutorial of CKafka Client
- Connector Practical Tutorial
- Reporting over HTTP
- Querying Subscription to Database Change Info
- Log Access
- Troubleshooting
- Topic Failures
- Consumer Group Failures
- Client Failures
- API Documentation
- Making API Requests
- DataHub APIs
- ACL APIs
- Topic APIs
- Instance APIs
- Other APIs
- SDK Documentation
- SDK for Java
- SDK for Python
- SDK for Node.js
- SDK for Connector
- Elastic Topic Message Sending and Receiving
- General References
- Connector
- Database Change Subscription
- FAQs
Connecting Kafka Connect to CKafka
마지막 업데이트 시간:2024-01-09 14:56:36
Kafka Connect currently supports two execution modes: standalone and distributed.
Starting Connect in Standalone Mode
Start Connect in standalone mode by running the following command:
bin/connect-standalone.sh config/connect-standalone.properties connector1.properties [connector2.properties ...]
Accessing CKafka is basically the same as accessing the open-source Kafka, except that you need to change the value of
bootstrap.servers to the IP address assigned when you apply for the instance.Starting Connect in Distributed Mode
Start Connect in distributed mode by running the following command:
bin/connect-distributed.sh config/connect-distributed.properties
In this mode, Kafka Connect stores the offset, configuration, and task status information in Kafka topics, which are configured in the following fields in
connect-distributed:config.storage.topicoffset.storage.topicstatus.storage.topic
These topics need to be created manually to ensure that their attributes meet the requirements of Connect.
config.storage.topic should have only one partition and multiple replicas and be in compact mode.offset.storage.topic should have multiple partitions and replicas and be in compact mode.status.storage.topic should have multiple partitions and replicas and be in compact mode.Set
bootstrap.servers to the IP address assigned when you apply for the instance.Configure
group.id to identify the Connect cluster, which should be differentiated from the consumer group.