You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Swapnil Ghike (JIRA)" <ji...@apache.org> on 2012/09/06 04:11:07 UTC

[jira] [Updated] (KAFKA-490) Check max message size on server instead of producer

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

Swapnil Ghike updated KAFKA-490:
--------------------------------

    Attachment: kafka-490-v2.patch

attached the modified patch. I dont know if it will need a rebase, svn is still down.
                
> Check max message size on server instead of producer
> ----------------------------------------------------
>
>                 Key: KAFKA-490
>                 URL: https://issues.apache.org/jira/browse/KAFKA-490
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.8
>            Reporter: Swapnil Ghike
>            Assignee: Swapnil Ghike
>              Labels: bug
>             Fix For: 0.8
>
>         Attachments: kafka-490-v1.patch, kafka-490-v2.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Message size is checked currently only in SyncProducer and not at the server. Therefore, non-java clients can push bigger messages to the server. Need a message size check at the server. Can remove the check from producer side since server can send acks in 0.8.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira