Child pages
  • KAFKA-656 - Quota Design
Skip to end of metadata
Go to start of metadata

Quota Implementation KAFKA-656


There are several quantities we would want to track: 
1. Requests pers second 
2. Bytes written per second 
3. Bytes read per second 

There are two reasonable groupings we would want to aggregate and enforce these thresholds at: 
1. Topic level 
2. Client level (e.g. by client id from the request) 

When a request hits one of these limits we will simply reject it with a QUOTA_EXCEEDED exception.

Conceptual Design:

This is psuedo-code obviously, and incomplete, just starting to put some ideas down. 

  • No labels

1 Comment

  1. Anonymous

    I just wanted to comment on your blog and say I really enjoyed reading your blog here. It was very informative and I also digg the way you write! Keep it up and I'll be back soon to find out more mate.HDD player