[jira] [Updated] (KAFKA-766) Isr shrink/expand check is fragile
[ https://issues.apache.org/jira/browse/KAFKA-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-766: Fix Version/s: 0.8.3 > Isr shrink/expand check is fragile > -- > > Key: KAFKA-766 > URL: https://issues.apache.org/jira/browse/KAFKA-766 > Project: Kafka > Issue Type: Bug >Affects Versions: 0.8.0 >Reporter: Sriram Subramanian >Assignee: Neha Narkhede > Fix For: 0.8.3 > > > Currently the isr check is coupled tightly with the produce batch size. For > example, if the producer batch size is 1 messages and isr check is 4000 > messages, we continuously oscillate between shrinking isr and expanding isr > every second. This is because a single produce request throws the replica out > of the isr. This results in hundreds of calls to ZK (we still dont have multi > write). This can be alleviated by making the producer batch size smaller than > the isr check size. > Going forward, we should try to not have this coupling. It is worth > investigating if we can make the check more robust under such scenarios. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-766) Isr shrink/expand check is fragile
[ https://issues.apache.org/jira/browse/KAFKA-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-766: Fix Version/s: (was: 0.8.1) > Isr shrink/expand check is fragile > -- > > Key: KAFKA-766 > URL: https://issues.apache.org/jira/browse/KAFKA-766 > Project: Kafka > Issue Type: Bug >Affects Versions: 0.8.0 >Reporter: Sriram Subramanian >Assignee: Neha Narkhede > > Currently the isr check is coupled tightly with the produce batch size. For > example, if the producer batch size is 1 messages and isr check is 4000 > messages, we continuously oscillate between shrinking isr and expanding isr > every second. This is because a single produce request throws the replica out > of the isr. This results in hundreds of calls to ZK (we still dont have multi > write). This can be alleviated by making the producer batch size smaller than > the isr check size. > Going forward, we should try to not have this coupling. It is worth > investigating if we can make the check more robust under such scenarios. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (KAFKA-766) Isr shrink/expand check is fragile
[ https://issues.apache.org/jira/browse/KAFKA-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-766: Fix Version/s: (was: 0.8) 0.8.1 > Isr shrink/expand check is fragile > -- > > Key: KAFKA-766 > URL: https://issues.apache.org/jira/browse/KAFKA-766 > Project: Kafka > Issue Type: Bug >Affects Versions: 0.8 >Reporter: Sriram Subramanian >Assignee: Neha Narkhede > Fix For: 0.8.1 > > > Currently the isr check is coupled tightly with the produce batch size. For > example, if the producer batch size is 1 messages and isr check is 4000 > messages, we continuously oscillate between shrinking isr and expanding isr > every second. This is because a single produce request throws the replica out > of the isr. This results in hundreds of calls to ZK (we still dont have multi > write). This can be alleviated by making the producer batch size smaller than > the isr check size. > Going forward, we should try to not have this coupling. It is worth > investigating if we can make the check more robust under such scenarios. -- 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
