[ https://issues.apache.org/jira/browse/KAFKA-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208940#comment-14208940 ]
Joel Koshy commented on KAFKA-1762: ----------------------------------- Committed the doc change to trunk > Enforce MAX_IN_FLIGHT_REQUESTS_PER_CONNECTION to 1 in MirrorMaker > ----------------------------------------------------------------- > > Key: KAFKA-1762 > URL: https://issues.apache.org/jira/browse/KAFKA-1762 > Project: Kafka > Issue Type: Bug > Reporter: Guozhang Wang > Assignee: Guozhang Wang > Attachments: KAFKA-1762.patch > > > The new Producer client introduces a config for the max # of inFlight > messages. When it is set > 1 on MirrorMaker, however, there is a risk for > data loss even with KAFKA-1650 because the offsets recorded in the MM's > offset map is no longer continuous. > Another issue is that when this value is set > 1, there is a risk of message > re-ordering in the producer > Changes: > 1. Set max # of inFlight messages = 1 in MM > 2. Leave comments explaining what the risks are of changing -- This message was sent by Atlassian JIRA (v6.3.4#6332)