Rework mqtt_consumer connect/reconnect#4846
Conversation
|
@danielnelson sorry for slow action. It is the first time I contribute to community and just learned golang few weeks ago so I need a bit of time to check one by one carefully Your changes is pretty good. Here is my comment:
I will test it on our IoTs project to see how it is. Thanks |
|
Please make armhf build for RaspberryPi3 |
|
There is to output at all. /home/pi/telegraf --debug -config /etc/telegraf/telegraftest.conf publishing: debug with mosquitto_sub -u 'user' -P 'pass' -v -t 'test/#': mosquitto.log |
|
Using telegraf_1.9.0~dcf4fb4b-0_amd64.deb the problem of double connection we had with 1.8.0 and 1.8.1 is not present. MQTT messages are correctly received. (we haven't tested reconnect yet). |
|
Yes. Now works stable (after restarting telegraf or mosquitto). |
|
Works as expected with telegraf_1.9.0~2cc071d4-0_amd64.deb:
NOTE: tested with |
|
Works perfectly so far on a RPi3 with telegraf_1.9.0%7E2cc071d4-0_armhf.deb |
|
telegraf_1.9.0%7E2cc071d4-0_armhf.deb works for me on a raspberry pi 1 using debian stretch |
(cherry picked from commit 152365a)
Reworks the connection lifetime for the mqtt_consumer plugin. For now I have this marked for 1.9.0 but if we can get some help testing we can consider it for 1.8.x.
closes #4594
closes #4580
closes #4731
Based on #4814
Required for all PRs: