fix: try increasing sarama library retry parameters

[reimda]

Test whether using sarama retry mechanisms apply to connection errors.

related #9778

[telegraf-tiger]

Looks like new artifacts were built from this PR. Get them here!

Artifact URLs

• armel.rpm

• linux_armel.tar.gz

• armel.deb

• linux_mips.tar.gz

• mips.deb

• s390x.rpm

• linux_s390x.tar.gz

• s390x.deb

• aarch64.rpm

• linux_arm64.tar.gz

• arm64.deb

• linux_mipsel.tar.gz

• mipsel.deb

• armv6hl.rpm

• freebsd_armv7.tar.gz

• linux_armhf.tar.gz

• armhf.deb

• linux_i386.tar.gzi386.rpm

• freebsd_i386.tar.gz

• i386.deb

• static_linux_amd64.tar.gz

• x86_64.rpm

• freebsd_amd64.tar.gz

• linux_amd64.tar.gz

• amd64.deb

• ppc64le.rpm

• linux_ppc64le.tar.gz

• ppc64el.deb

• windows_amd64.zip

• windows_i386.zip

• darwin_amd64.tar.gz

[powersj]

FYI these were the options I could play with to adjust the retry mechanism of sarama:

Metadata.Retry.Max (default: 5)
Metadata.Retry.Backoff (default: 250ms)

[powersj]

@reimda next steps on this one? or happy to close?