GitHub user cnZach opened a pull request:
https://github.com/apache/kafka/pull/4125
KAFKA-6105: load client properties in proper order for EndToEndLatency tool
Currently, the property file is loaded first, and later a auto generated
group.id is used:
consumerProps.put
Github user cnZach closed the pull request at:
https://github.com/apache/kafka/pull/4116
---
GitHub user cnZach opened a pull request:
https://github.com/apache/kafka/pull/4116
KAFKA-6105: load client properties in proper order for EndToEndLatency tool
Currently, the property file is loaded first, and later a auto generated
group.id is used:
`consumerProps.put
Github user cnZach closed the pull request at:
https://github.com/apache/kafka/pull/4115
---
Github user cnZach closed the pull request at:
https://github.com/apache/kafka/pull/3512
---
GitHub user cnZach opened a pull request:
https://github.com/apache/kafka/pull/4115
KAFKA-6105: load client properties in proper order for
kafka.tools.EndToEndLatency
Currently, the property file is loaded first, and later a auto generated
group.id is used:
consumerProps.put
GitHub user cnZach opened a pull request:
https://github.com/apache/kafka/pull/3512
KAFKA-5574: add thread.id header in show-detailed-stats report
kafka-consumer-perf-test.sh report missing one header column:
time, data.consumed.in.MB, MB.sec, data.consumed.in.nMsg