[jira] [Updated] (KAFKA-1762) Update max-inflight-request doc string
[ https://issues.apache.org/jira/browse/KAFKA-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-1762: - Fix Version/s: 0.8.3 > Update max-inflight-request doc string > -- > > Key: KAFKA-1762 > URL: https://issues.apache.org/jira/browse/KAFKA-1762 > Project: Kafka > Issue Type: Bug >Reporter: Guozhang Wang >Assignee: Guozhang Wang > Fix For: 0.8.3 > > 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)
[jira] [Updated] (KAFKA-1762) Update max-inflight-request doc string
[ https://issues.apache.org/jira/browse/KAFKA-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-1762: -- Summary: Update max-inflight-request doc string (was: Enforce MAX_IN_FLIGHT_REQUESTS_PER_CONNECTION to 1 in MirrorMaker) > Update max-inflight-request doc string > -- > > 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)
[jira] [Updated] (KAFKA-1762) Update max-inflight-request doc string
[ https://issues.apache.org/jira/browse/KAFKA-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-1762: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Update max-inflight-request doc string > -- > > 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)
