-
Notifications
You must be signed in to change notification settings - Fork 367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: MalformedInputException in MQTT Source connector in Azure K8s #939
Comments
@mukkchir thanks for the detailed report. Is it possible that your default charset is set to something different to UTF-8? Please could you try this build that I have prepared, with a possible fix. Let me know how it goes. |
@davidsloan you are really a lifesaver and huge kudos to you for giving me a quick fix. It's working! |
@davidsloan The connector is constantly looping over "error handling message on topic" and re-subscribing to topic with error description below:
Not sure what is happening. How to properly handle this in the connector config? Also, what happens if the task.max is set to 2 or more? |
@mukkchir are you able to send me some samples of your data? This would help troubleshooting this issue. You can find me on our community slack if you are not comfortable sending it on here. It is not obvious to me what the problem is without more information. |
@davidsloan Sure! Here is the sample data on which the error is occurring:
|
I'm sorry I'm not seeing a problem with this input I've put together a quick test here which you can see is working: Is this message any different from previous messages? Is there any schema change, missing/added fields etc here since the preceding message? |
@davidsloan This is just the sample data. Since the data is encrypted, I'm working on decrypting it. I will post the actual data soon. Is there a config where I can move to next message if the previous message is faulty? |
@davidsloan I've got the same issue with the jms source connector. When can we expect a release with the fix included? Thank you very much 🙏. |
@davidsloan seems like its the same data which I posted here. |
@mukkchir this is message id 3, correct? Are message id 1 & 2 any different? |
@mukkchir it seems like the issue might be that a different charset encoding is being configured by default. Please can you try setting this environment variable in the Connect container:
And let me know how you get on. |
Hey, @davidsloan I tried the AC_ALL=en_US.UTF-8 but it was ignore by the bash at the beginning of the connect: Thanks. |
Hi @davidsloan, I'm now using the "sink connector" and I have the same problem with the malformed input. Thanks a lot, Erez. |
Im using mqtt connector inside debezium kafka connect docker, the issue was solved by adding LANG=en_US.UTF-8 variable to docker container |
Hi,
I have deployed Strimzi kafka clusters in azure k8s. After deploying the MQTT source connector, I get the following error upon
kubectl describe kctr -n kafka
-Error Trace
MQTT source connector config
Strimzi kafka config
Steps to reproduce in azure k8s
Previously used versions
Currently used versions
In both of these versions, the same error above persisted. I think I'm missing some config but not sure what it is. Any guidance will be greatly helpful.
The text was updated successfully, but these errors were encountered: