codelipenghui commented on issue #2876: Limit the client reconnect behavior. URL: https://github.com/apache/pulsar/issues/2876#issuecomment-435292468 I think more secure and unified on broker side, broker already limit the maxConsumersPerTopic and maxConsumersPerSubscription, broker limit the client reconnect(actually limit subscribe) is taken for granted. If on client side, every client should implement this limiter. But to identify consumer, on client side is more simple. On broker side, broker can get the consumerId, consumerName, ip address. Is consumerName + consumerId is unique ? If broker can identify consumer, we just add a subscribe limiter on broker/namespace level. When broker handle subscribe request should check the limiter. When client got the limit error, client retry again. Subscribe limiter config in broker.conf. limiter support 2 parameters of resetPeriod and maxSubscribePerConsumer. On client side, it's necessary to add metrics record the re-connect times.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
