You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ewen Cheslack-Postava (JIRA)" <ji...@apache.org> on 2016/11/14 00:48:59 UTC

[jira] [Resolved] (KAFKA-3967) Excessive Network IO between Kafka brokers

     [ https://issues.apache.org/jira/browse/KAFKA-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ewen Cheslack-Postava resolved KAFKA-3967.
------------------------------------------
    Resolution: Invalid

[~Krishna82] Closing this for now since we haven't heard back. If there are some details that were missing in the initial report that show this is actually an unexpectedly high throughput for replication, please reopen and add some more details.

> Excessive Network IO between Kafka brokers 
> -------------------------------------------
>
>                 Key: KAFKA-3967
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3967
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.8.2.2
>            Reporter: Krishna
>
> Excessive Network IO between Kafka brokers running on AWS in different AZ's as compared to actual message volume. 
> We are producing  2-5 MB /Sec message volume however kafka seems to me moving 20 gb /hr on network. The data volume has around 12 GB of message log on each nodes. Is this a natural behavior ?. I believe only the new messages will get replicated on non-leader nodes however here it seems that entire log is re-synced  



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