What Should I Do If Data Fails to Be Dumped Using a VPCEP Channel?
Symptom
A dump task is successfully added, but the data dump does not take effect or the task status is Disabled. The possible causes are as follows. You can locate the root cause based on the displayed information.
Cause 1: TCP Port 9011 Is Not Allowed in the Security Group
A dump task is successfully added and the task status is normal. However, the dumped data cannot be found in the dump destination or there is a delay. This may be caused by differences in the forwarding link configuration. The VPCEP channel communicates through TCP port 9011. Although the channel is successfully established, traffic may be intercepted, resulting in data forwarding failures. Therefore, you need to check whether an inbound rule of the security group used by the Kafka instance allows traffic from TCP port 9011. Perform the following steps:
- Log in to the Kafka console.
- On the Kafka Instances page, click the name of a Kafka instance.
- In the Network area on the Overview page, view and copy the name of the security group bound to the Kafka instance.
- Go to the Security Groups page.
- Click the search box and search for the security group using information obtained in step 3.
- Click the security group name to go to the details page.
- Click the Inbound Rules tab.
- Check whether TCP port 9011 is enabled in an inbound rule.
- If not, add a rule by referring to Table 1. After the rule is added, you do not need to create the dump task again. The channel will automatically resume data forwarding. If the problem persists, submit a service ticket to contact O&M personnel.
- If yes, submit a service ticket to contact O&M personnel.
Cause 2: The Kafka Instance Is Deleted
After a dump task is added, if the Kafka instance on which the task depends is deleted, the dump destination displays "The resource is abnormal." and the task status is automatically updated to Disabled and cannot be manually enabled.
Log in to the Kafka console and check whether the target Kafka cluster has been deleted from the instance list. If yes, delete the dump task and add it again.
Cause 3: The Connection Request of the VPC Endpoint Service Is Rejected
After a dump task is added, if the connection request to the VPC endpoint service on which the task depends is rejected, Cloud Eye automatically updates the status of the dump task to Disabled and the task cannot be manually enabled. Perform the following steps to check whether the VPC endpoint connection to the VPC endpoint service is rejected. If yes, delete the dump task and add it again.
- Log in to the Kafka console.
- On the Kafka Instances page, click the name of a Kafka instance.
- In the Network area on the Overview page, view and copy the name of the VPC bound to the Kafka instance.
- Log in to the VPC Endpoint Services page.
- Click the search box and search for the VPC endpoint service using the VPC name obtained in step 3.
- Click the name of the VPC endpoint service to go to the details page.
- Click the Connection Management tab to view the VPC endpoint connected to the VPC endpoint service.
If Status of the VPC endpoint is Rejected, the connection request to the VPC endpoint service on which the task depends has been rejected.
Cause 4: The VPC Endpoint Service on Which the Dump Task Depends Has Been Deleted
After a dump task is added, if the VPC endpoint service on which the task depends is deleted, the task status automatically changes to Disabled and cannot be manually enabled. Perform the following steps to check whether the target VPC endpoint service has been deleted. If yes, delete the dump task and add it again.
- Log in to the Kafka console.
- On the Kafka Instances page, click the name of a Kafka instance.
- In the Network area on the Overview page, view and copy the name of the VPC bound to the Kafka instance.
- Log in to the VPC Endpoint Services page.
- Click the search box and search for the VPC endpoint service using the VPC name obtained in step 3. If the search result does not contain the VPC endpoint service created by Cloud Eye, the VPC endpoint service on which the dump task depends has been deleted.
The name of a VPC endpoint service created by Cloud Eye is in the format of regionName+.+serviceName+.+serviceId, for example, cn-north-4.ces-data-share.84b76e40-10f7-4fa1-93b8-37628339XXXX.
Cause 5: The Kafka Instance Is Scaled In or Out
After a dump task is added, if the Kafka instance on which the task depends is scaled in or out, the broker configuration (quantity or IP:Port) will change. When Cloud Eye detects that the broker configuration has changed, it clears the endpoint of the Kafka instance and updates the status of the associated data dump task to Disabled. The task cannot be manually enabled. In this case, delete the dump task and add it again.
Cause 6: Ciphertext Access Is Not Enabled for the Kafka Instance, or the Username or Password Has Been Changed
When adding a dump task using a VPCEP channel, you need to configure the username and password of the Kafka instance. If ciphertext access is not enabled for the Kafka instance on which the dump task depends, or the username or password for ciphertext access has been changed, the authentication credential changes. As a result, the authentication fails, the dump task status automatically changes to Disabled, and the task cannot be manually enabled. In this case, delete the dump task and add a new one using the new username and password.
Submitting a Service Ticket
If the problem persists, submit a service ticket.
What Should I Pay Attention to When Adding a Dump Task Again?
- The Kafka instance is running properly and has not been deleted.
- The username and password of the Kafka instance are valid.
- An inbound rule of the security group used by the Kafka instance allows traffic from TCP port 9011.
- The Kafka instance is not bound to an endpoint service.
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot