Profiling a Kafka Streams job revealed some hotspots in the Fetcher during metrics flushing. Previous discussion here:
- is related to
-
KAFKA-3769 KStream job spending 60% of time writing metrics
-
- Resolved
-
- links to