Another question about using kafka recently:

Currently, Kafka's write throttle only supports the user dimension and clientId 
dimension of the request. In fact, such a situation is often encountered in 
actual use: a topic entry traffic suddenly increases, and the resource 
bottleneck is about to be reached. It needs to be restricted, but The user 
and/or clientId written to this topic also send data to other topics in this 
cluster, which may affect other topics, and it is impossible to make an 
effective restriction on a single topic. Do we have plans to add throttle in 
topic dimension?

Reply via email to