thetumbled commented on PR #4645: URL: https://github.com/apache/bookkeeper/pull/4645#issuecomment-3138401968
> I think adding a gcRateLimiter doesn't fundamentally solve the problem, nor is it practically feasible to implement or limit the number of calls. Why? I believe adding a rate limiter and acquiring it prior to each zk operation would suffice. > I think it could be more practical to break down the rate limits into several categories: rate limits for GC calls to ZooKeeper, rate limits for GC file reads, rate limits for GC file writes, or rate limits for other GC resources. We haven't encountered any issues with GC file reads or writes. The only thing I need to limit is the rate of zk reads. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
