RocketMQ Pre-check
Checking the Source and Target Instance Versions
- Check whether the source and target instance versions meet the requirements. Currently, the RocketMQ instance version must be 5.x or 4.8.0. If the version is not in the matching list, a warning is generated.
- Cause 1: The source RocketMQ instance version is not supported. Select a supported instance.
Solution: Go to the Configure Source and Target page of the professional event stream job and select a source instance that meets the version requirements.
- Cause 2: The target RocketMQ instance version is not supported. Select a supported instance.
Solution: Go to the Configure Source and Target page of the professional event stream job and select a target instance that meets the version requirements.
- Cause 1: The source RocketMQ instance version is not supported. Select a supported instance.
- Check whether the source and target RocketMQ instances are of the same version. If not, a warning is generated.
Cause: The source and target instances are of different versions. Check their versions.
Solution: Check whether the source and target RocketMQ instance versions are the same in the Configure Source and Target page. If they are different, modify the source or target instance to ensure that they are the same.
Checking the Source Connectivity
- Cause 1: The source RocketMQ instance cannot be connected. Check whether the network configuration is correct.
- On the RocketMQ console, check whether the source instance is normal.
- Check whether the VPC and subnet of the event stream cluster can connect to the source RocketMQ instance.
- Cause 2: The source RocketMQ instance cannot be connected. Check whether the entered instance information is correct.
- On the RocketMQ console, check whether the source instance is normal.
- Check whether the VPC and subnet of the event stream cluster can connect to the source RocketMQ instance.
- Check whether the username and password of the source RocketMQ instance configured on the Configure Source and Target page are correct.
Checking the Target Connectivity
Check whether the VM where the event stream job is located can connect to the target RocketMQ instance.
- Cause 1: The target RocketMQ instance cannot be connected. Check whether the network configuration is correct.
- On the RocketMQ console, check whether the target instance is normal.
- Check whether the VPC and subnet of the event stream cluster can connect to the target RocketMQ instance.
- Cause 2: The target RocketMQ instance cannot be connected. Check whether the entered instance information is correct.
- On the RocketMQ console, check whether the target instance is normal.
- Check whether the VPC and subnet of the event stream cluster can connect to the target RocketMQ instance.
- Check whether the username and password of the target RocketMQ instance configured on the Configure Source and Target page are correct.
Checking the Source and Target Instance Specifications
- Check whether the specifications of the source and target RocketMQ instances match.
Cause: The brokers of the source and target RocketMQ instances are inconsistent.
Solution: Check whether the source and target RocketMQ instance brokers are the same in the Configure Source and Target page. If not, modify the source or target instance to ensure that they are the same.
- Check whether the specifications of the source and target RocketMQ instances match.
Cause: The specifications of the source and target RocketMQ instances are inconsistent.
Solution: Check whether the source and target RocketMQ instance types are the same in the Configure Source and Target page. If not, modify the source or target instance to ensure that they are the same.
Checking the Addresses of the Source and Target Instances
Check whether the source and target instance have the same IP address.
Cause: The source and target RocketMQ instances have the same IP address. Check the node IP addresses of the source and target instances.
Solution: Check the node connection addresses and IP addresses of the source and target instances. If they use the same IP address, modify either the source or target instance to ensure the IP addresses are unique.
Feedback
Was this page helpful?
Provide feedbackThank 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