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

Posted to dev@kafka.apache.org by "Joe Stein (JIRA)" <ji...@apache.org> on 2015/01/15 19:21:35 UTC

[jira] [Comment Edited] (KAFKA-1697) remove code related to ack>1 on the broker

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

Joe Stein edited comment on KAFKA-1697 at 1/15/15 6:21 PM:
-----------------------------------------------------------

With this patch I think we should change the existing functionality with > 1 update to start to LOG as a WARN in the Broker (so it gets people attention to stop using ack >1) but keep everything else the same... the new version of the request (with a match/case) should do the new functionality and we support both.


was (Author: joestein):
With this patch I think we should change the existing functionality with 1 update to start to LOG as a WARN in the Broker (so it gets people attention to stop using ack >1) but keep everything else the same... the new version of the request (with a match/case) should do the new functionality.

> remove code related to ack>1 on the broker
> ------------------------------------------
>
>                 Key: KAFKA-1697
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1697
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Jun Rao
>            Assignee: Gwen Shapira
>             Fix For: 0.8.3
>
>         Attachments: KAFKA-1697.patch, KAFKA-1697_2015-01-14_15:41:37.patch
>
>
> We removed the ack>1 support from the producer client in kafka-1555. We can completely remove the code in the broker that supports ack>1.
> Also, we probably want to make NotEnoughReplicasAfterAppend a non-retriable exception and let the client decide what to do.



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