[jira] [Commented] (KAFKA-1537) add request.required.acks=-2 to require acks from all replicas
[ https://issues.apache.org/jira/browse/KAFKA-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069607#comment-14069607 ] Jiang Wu commented on KAFKA-1537: - I agree that adding acks=-2 to require acks from all replicas is not necessary; mainly because users can do so by setting acks=num_of_replicas. > add request.required.acks=-2 to require acks from all replicas > -- > > Key: KAFKA-1537 > URL: https://issues.apache.org/jira/browse/KAFKA-1537 > Project: Kafka > Issue Type: Improvement > Components: core >Affects Versions: 0.8.1.1 >Reporter: Jiang Wu >Priority: Minor > > The current options for the producer parameter request.required.acks include > 0, positive numbers and -1. -1 means the acks from replicas in ISR. > In a stress test, it's found that, if request.required.acks=-1 and the leader > is receiving at high speed, then the followers will fail out of ISR. In this > case, request.required.acks=-1 is equivelant to request.required.acks=1 > because only the leader is in ISR. > It would be desirable to add request.required.acks=-2 to require acks from > all replicas. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (KAFKA-1537) add request.required.acks=-2 to require acks from all replicas
[ https://issues.apache.org/jira/browse/KAFKA-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069509#comment-14069509 ] Daniel Compton commented on KAFKA-1537: --- Adding to that, you will have less availability (though more durability) than running a single broker, as you now have 3 independent nodes that can fail, any of which will stop further writes. More information on this is in the Discussion session on http://aphyr.com/posts/293-call-me-maybe-kafka > add request.required.acks=-2 to require acks from all replicas > -- > > Key: KAFKA-1537 > URL: https://issues.apache.org/jira/browse/KAFKA-1537 > Project: Kafka > Issue Type: Improvement > Components: core >Affects Versions: 0.8.1.1 >Reporter: Jiang Wu >Priority: Minor > > The current options for the producer parameter request.required.acks include > 0, positive numbers and -1. -1 means the acks from replicas in ISR. > In a stress test, it's found that, if request.required.acks=-1 and the leader > is receiving at high speed, then the followers will fail out of ISR. In this > case, request.required.acks=-1 is equivelant to request.required.acks=1 > because only the leader is in ISR. > It would be desirable to add request.required.acks=-2 to require acks from > all replicas. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (KAFKA-1537) add request.required.acks=-2 to require acks from all replicas
[ https://issues.apache.org/jira/browse/KAFKA-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059451#comment-14059451 ] Jay Kreps commented on KAFKA-1537: -- Wouldn't it be somewhat odd that you actually want to require N/N replicas to acknowledge? It seems more likely that if you have replication factor 3 you would want 2 acks, which we already support today. Otherwise you have no fault-tolerance. > add request.required.acks=-2 to require acks from all replicas > -- > > Key: KAFKA-1537 > URL: https://issues.apache.org/jira/browse/KAFKA-1537 > Project: Kafka > Issue Type: Improvement > Components: core >Affects Versions: 0.8.1.1 >Reporter: Jiang Wu >Priority: Minor > > The current options for the producer parameter request.required.acks include > 0, positive numbers and -1. -1 means the acks from replicas in ISR. > In a stress test, it's found that, if request.required.acks=-1 and the leader > is receiving at high speed, then the followers will fail out of ISR. In this > case, request.required.acks=-1 is equivelant to request.required.acks=1 > because only the leader is in ISR. > It would be desirable to add request.required.acks=-2 to require acks from > all replicas. -- This message was sent by Atlassian JIRA (v6.2#6252)
