[jira] [Updated] (KAFKA-4225) Replication Quotas: Control Leader & Follower Limit Separately
[ https://issues.apache.org/jira/browse/KAFKA-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-4225: --- Status: Resolved (was: Closed) > Replication Quotas: Control Leader & Follower Limit Separately > -- > > Key: KAFKA-4225 > URL: https://issues.apache.org/jira/browse/KAFKA-4225 > Project: Kafka > Issue Type: Bug >Affects Versions: 0.10.1.0 >Reporter: Ben Stopford >Assignee: Ben Stopford > Fix For: 0.10.1.0 > > > As we split the throttled replicas into Leader and Follower configs, it makes > sense to also split the throttle limit: > replication.quota.throttled.rate >=> > replication.leader.quota.throttled.rate > & > replication.follower.quota.throttled.rate > So that admins have fine grain control over both sides of the replication > process and the properties match for leader/follower applicability. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-4225) Replication Quotas: Control Leader & Follower Limit Separately
[ https://issues.apache.org/jira/browse/KAFKA-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4225: --- Fix Version/s: 0.10.1.0 > Replication Quotas: Control Leader & Follower Limit Separately > -- > > Key: KAFKA-4225 > URL: https://issues.apache.org/jira/browse/KAFKA-4225 > Project: Kafka > Issue Type: Bug >Affects Versions: 0.10.1.0 >Reporter: Ben Stopford >Assignee: Ben Stopford > Fix For: 0.10.1.0 > > > As we split the throttled replicas into Leader and Follower configs, it makes > sense to also split the throttle limit: > replication.quota.throttled.rate >=> > replication.leader.quota.throttled.rate > & > replication.follower.quota.throttled.rate > So that admins have fine grain control over both sides of the replication > process and the properties match for leader/follower applicability. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-4225) Replication Quotas: Control Leader & Follower Limit Separately
[ https://issues.apache.org/jira/browse/KAFKA-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford updated KAFKA-4225: Description: As we split the throttled replicas into Leader and Follower configs, it makes sense to also split the throttle limit: replication.quota.throttled.rate => replication.leader.quota.throttled.rate & replication.follower.quota.throttled.rate So that admins have fine grain control over both sides of the replication process and the properties match for leader/follower applicability. was: As we split the throttled replicas into Leader and Follower configs, it makes sense to also split the throttle limit: replication.quota.throttled.rate => replication.leader.quota.throttled.rate & replication.leader.quota.throttled.rate So that admins have fine grain control over both sides of the replication process and the properties match for leader/follower applicability. > Replication Quotas: Control Leader & Follower Limit Separately > -- > > Key: KAFKA-4225 > URL: https://issues.apache.org/jira/browse/KAFKA-4225 > Project: Kafka > Issue Type: Bug >Affects Versions: 0.10.1.0 >Reporter: Ben Stopford >Assignee: Ben Stopford > > As we split the throttled replicas into Leader and Follower configs, it makes > sense to also split the throttle limit: > replication.quota.throttled.rate >=> > replication.leader.quota.throttled.rate > & > replication.follower.quota.throttled.rate > So that admins have fine grain control over both sides of the replication > process and the properties match for leader/follower applicability. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-4225) Replication Quotas: Control Leader & Follower Limit Separately
[ https://issues.apache.org/jira/browse/KAFKA-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Stopford updated KAFKA-4225: Assignee: Ben Stopford Affects Version/s: 0.10.1.0 > Replication Quotas: Control Leader & Follower Limit Separately > -- > > Key: KAFKA-4225 > URL: https://issues.apache.org/jira/browse/KAFKA-4225 > Project: Kafka > Issue Type: Bug >Affects Versions: 0.10.1.0 >Reporter: Ben Stopford >Assignee: Ben Stopford > > As we split the throttled replicas into Leader and Follower configs, it makes > sense to also split the throttle limit: > replication.quota.throttled.rate >=> > replication.leader.quota.throttled.rate > & > replication.leader.quota.throttled.rate > So that admins have fine grain control over both sides of the replication > process and the properties match for leader/follower applicability. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
