Closed polo0987 closed 9 months ago
version infor:
Hello @polo0987
That's a good catch and thanks for reporting Is that possible for you to share the jmeter.log file.
I guess it's most likely to be a deprecated flag and the below is what I found in official doc.
metadata.fetch.timeout.ms and timeout.ms have been removed. They were initially deprecated in Kafka 0.9.0.0.
but I will double check and update the repo's wiki.
Basically the wiki is outdated with the configs which can be used on producer and consumer
It is wise to refer the below docs until wiki is fixed:
In sometime - i will update the wiki, i will appreciate - if you have time to create a PR as well
Thanks for your advice.
From https://kafka.apache.org/documentation/#consumerconfigs, the config property "metadata.fetch.timeout.ms" has removed.
and what I want is to set the time for consumer client getting the metadata, the default value is 60 seconds, it is too long for me. any other config property can be used? could you please give me some suggestion?
while, the property "metadata.fetch.timeout.ms" for producer client seem to be useful.
Here is the jmeter.log jmeter.log
Since the metadata.fetch.timeout.ms
flag in the Kafka client has been officially deprecated.
I would suggest to post a query on Stack Overflow to find a suitable replacement. The plugin is designed to easily adopt these configurations, so introducing the required configurations won’t be an issue.
yes, got it.
and, maybe, just need to update the document https://github.com/rollno748/di-kafkameter/wiki#consumer-properties
Yes, I will do it in free time and as said contributions are always welcome ! Marking this as not a bug and closing it - feel free to re-open it, if you feel so
create a issue - if you found a bug star it - if you find this as useful :)
The consumer config property 'metadata.fetch.timeout.ms' is failed to apply screenshot:![image](https://github.com/rollno748/di-kafkameter/assets/16302551/a9f31176-88ce-4d07-878d-8c046ed7e040)