[ 
https://issues.apache.org/jira/browse/KAFKA-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14305971#comment-14305971
 ] 

Steven Zhen Wu commented on KAFKA-1919:
---------------------------------------

this is the producer metrics when cpu shoot up to 100% on one core. it clears 
shows request rate shoot up to the roof.
 [request-rate] 18716.091686350177

{code}
main 13:10:54,254  INFO EmptyTopicTest:52 - [request-latency-avg] NaN
main 13:10:54,254  INFO EmptyTopicTest:52 - [outgoing-byte-rate] 
393038.5293628348
main 13:10:54,254  INFO EmptyTopicTest:52 - [batch-size-avg] NaN
main 13:10:54,254  INFO EmptyTopicTest:52 - [connection-close-rate] NaN
main 13:10:54,254  INFO EmptyTopicTest:52 - [record-size-max] -Infinity
main 13:10:54,255  INFO EmptyTopicTest:52 - [waiting-threads] 0.0
main 13:10:54,255  INFO EmptyTopicTest:52 - [record-queue-time-avg] NaN
main 13:10:54,255  INFO EmptyTopicTest:52 - [connection-count] 1.0
main 13:10:54,255  INFO EmptyTopicTest:52 - [metadata-age] 360.072
main 13:10:54,255  INFO EmptyTopicTest:52 - [request-size-max] 21.0
main 13:10:54,255  INFO EmptyTopicTest:52 - [records-per-request-avg] NaN
main 13:10:54,255  INFO EmptyTopicTest:52 - [record-retry-rate] NaN
main 13:10:54,256  INFO EmptyTopicTest:52 - [record-send-rate] NaN
main 13:10:54,256  INFO EmptyTopicTest:52 - [buffer-total-bytes] 3.3554432E7
main 13:10:54,256  INFO EmptyTopicTest:52 - [network-io-rate] 37432.278670526
main 13:10:54,256  INFO EmptyTopicTest:52 - [response-rate] 18715.822784810127
main 13:10:54,256  INFO EmptyTopicTest:52 - [io-wait-time-ns-avg] 
19766.866064623417
main 13:10:54,256  INFO EmptyTopicTest:52 - [compression-rate-avg] NaN
main 13:10:54,257  INFO EmptyTopicTest:52 - [incoming-byte-rate] 
224586.38952733087
main 13:10:54,257  INFO EmptyTopicTest:52 - [bufferpool-wait-ratio] NaN
main 13:10:54,257  INFO EmptyTopicTest:52 - [connection-creation-rate] NaN
main 13:10:54,257  INFO EmptyTopicTest:52 - [buffer-available-bytes] 3.3554432E7
main 13:10:54,257  INFO EmptyTopicTest:52 - [record-queue-time-max] -Infinity
main 13:10:54,257  INFO EmptyTopicTest:52 - [record-size-avg] NaN
main 13:10:54,258  INFO EmptyTopicTest:52 - [record-error-rate] NaN
main 13:10:54,258  INFO EmptyTopicTest:52 - [request-latency-max] -Infinity
main 13:10:54,258  INFO EmptyTopicTest:52 - [request-rate] 18716.091686350177
main 13:10:54,258  INFO EmptyTopicTest:52 - [batch-size-max] -Infinity
main 13:10:54,258  INFO EmptyTopicTest:52 - [io-time-ns-avg] 5109.803392094824
main 13:10:54,258  INFO EmptyTopicTest:52 - [select-rate] 37431.806091235536
main 13:10:54,259  INFO EmptyTopicTest:52 - [io-ratio] 0.19126365661468897
main 13:10:54,259  INFO EmptyTopicTest:52 - [requests-in-flight] 1.0
main 13:10:54,259  INFO EmptyTopicTest:52 - [io-wait-ratio] 0.7398999567776041
main 13:10:54,259  INFO EmptyTopicTest:52 - [request-size-avg] 21.0
{code}

> Metadata request issued with no backoff in new producer if there are no topics
> ------------------------------------------------------------------------------
>
>                 Key: KAFKA-1919
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1919
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.8.2
>            Reporter: Jay Kreps
>
> Original report:
> We have observed high cpu and high network traffic problem when
> 1) cluster (0.8.1.1) has no topic
> 2) KafkaProducer (0.8.2-beta) object is created without sending any traffic
> We have observed such problem twice. In both cases, problem went away
> immediately after one/any topic is created.
> Is this a known issue? Just want to check with the community first before I
> spend much time to reproduce it.
> I couldn't reproduce the issue with similar setup with unit test code in
> IDE. start two brokers with no topic locally on my laptop. create a
> KafkaProducer object without sending any msgs. but I only tested with
> 0.8.2-beta for both broker and producer.
> Issue exists in 0.8.2 as well:
> I have re-run my unit test with 0.8.2.0. same tight-loop problem happened
> after a few mins.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to