In case the broker is requesting a set of KIP 714 metrics that isn't matching any of librdkafka implemented metrics an assert is triggered that makes the client process terminate.
How to reproduceEnable the metric producer.request.latency.avg
on the cluster, this particular metric is only present in Java client.
Connect to the cluster with librdkafka 2.5.0.
Happens to clients already connected too.
Please provide the following information:
enable.metrics.push=true (default)
debug=..
as necessary) from librdkafka[rdkafka#producer-30][METADATA][7][thrd:main]: ssl://: 1/1 requested topic(s) seen in metadata (lookup by name)
[rdkafka#producer-30][CONTROLLERID][7][thrd:main]: ssl://: ControllerId update 2 -> 0
[rdkafka#producer-30][BROADCAST][7][thrd:main]: Broadcasting state change
[rdkafka#producer-19][PUSH][7][thrd:main]: Serializing metrics
[rdkafka#producer-19][PUSH][7][thrd:main]: Resource attributes count: 0
[rdkafka#producer-19][PUSH][7][thrd:main]: Total metrics to be encoded count: 0
[rdkafka#producer-19][PUSH][7][thrd:main]: Push Telemetry metrics encoded, size: 0
rdbuf.c:834: rd_slice_init_full: Assertion `r == 0' failed.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4