Hi Corey,

If you are already working with "rajadayalanvdm". Please go ahead.

Thanks,
Praveen.


-----Original Message-----
From: corey Kasten (JIRA) [mailto:j...@apache.org]
Sent: Wednesday, June 06, 2018 3:37 PM
To: jira@kafka.apache.org
Subject: [jira] [Commented] (KAFKA-7012) Performance issue upgrading to kafka 
1.0.1 or 1.1


    [ 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FKAFKA-7012%3Fpage%3Dcom.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel%26focusedCommentId%3D16503794%23comment-16503794&data=02%7C01%7Cpraveen.atluri%40kroger.com%7C832bf107ead44bd55c4b08d5cbe4e1dd%7C8331e14a91344288bf5a5e2c8412f074%7C0%7C0%7C636639106281015116&sdata=B92RC3iX6mANjP8VpFzRiwK%2FYAXWiojvhoryhLPjitM%3D&reserved=0
 ]

corey Kasten commented on KAFKA-7012:
-------------------------------------

Hi [~patl], I'm working with [~rajadayalanvdms] , and noticed you  have 
assigned this ticket to yourself. I just wanted to inquire about your 
expectations of when you'll have time to look into this ticket, etc. This will 
help us plan work on our side. Thank you!

> Performance issue upgrading to kafka 1.0.1 or 1.1
> -------------------------------------------------
>
>                 Key: KAFKA-7012
>                 URL: 
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FKAFKA-7012&data=02%7C01%7Cpraveen.atluri%40kroger.com%7C832bf107ead44bd55c4b08d5cbe4e1dd%7C8331e14a91344288bf5a5e2c8412f074%7C0%7C0%7C636639106281015116&sdata=hBaVIuCYJgYWDaJxo67gpm8mRFk466i4aaUQouRsb8s%3D&reserved=0
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.11.0.1, 1.1.0, 1.0.1
>            Reporter: rajadayalan perumalsamy
>            Assignee: praveen
>            Priority: Major
>         Attachments: Commit-47ee8e954-profile.png, 
> Commit-47ee8e954-profile2.png, Commit-f15cdbc91b-profile.png
>
>
> We are trying to upgrade kafka cluster from Kafka 0.11.0.1 to Kafka 1.0.1. 
> After upgrading 1 node on the cluster, we notice that network threads use 
> most of the cpu. It is a 3 node cluster with 15k messages/sec on each node. 
> With Kafka 0.11.0.1 typical usage of the servers is around 50 to 60% 
> vcpu(using less than 1 vcpu). After upgrade we are noticing that cpu usage is 
> high depending on the number of network threads used. If networks threads is 
> set to 8, then the cpu usage is around 850%(9 vcpus) and if it is set to 4 
> then the cpu usage is around 450%(5 vcpus). Using the same kafka 
> server.properties for both.
> Did further analysis with git bisect, couple of build and deploys, traced the 
> issue to commit 47ee8e954df62b9a79099e944ec4be29afe046f6. CPU usage is fine 
> for commit f15cdbc91b240e656d9a2aeb6877e94624b21f8d. But with commit 
> 47ee8e954df62b9a79099e944ec4be29afe046f6 cpu usage has increased. Have 
> attached screenshots of profiling done with both the commits. Screenshot 
> Commit-f15cdbc91b-profile shows less cpu usage by network threads and 
> Screenshots Commit-47ee8e954-profile and Commit-47ee8e954-profile2 show 
> higher cpu usage(almost entire cpu usage) by network threads. Also noticed 
> that kafka.network.Processor.poll() method is invoked 10 times more with 
> commit 47ee8e954df62b9a79099e944ec4be29afe046f6.
> We need the issue to be resolved to upgrade the cluster. Please let me know 
> if you need any additional information.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

________________________________

This e-mail message, including any attachments, is for the sole use of the 
intended recipient(s) and may contain information that is confidential and 
protected by law from unauthorized disclosure. Any unauthorized review, use, 
disclosure or distribution is prohibited. If you are not the intended 
recipient, please contact the sender by reply e-mail and destroy all copies of 
the original message.

Reply via email to