zhaizhibo commented on issue #4644: URL: https://github.com/apache/bookkeeper/issues/4644#issuecomment-3139551282
> I suggest describing the scenario more clearly, including specific scenarios and metrics. Or you could submit a BP-* to initiate this initiative. > > I personally think your requirements are overly complex and may not fit into BookKeeper's current ecosystem. When implementing Kafka on Pulsar, timeout is configured per request, not per broker. Kafka uses timewheel for timeouts, which doesn't align with Pulsar and BookKeeper client. During stress testing, we observed many write requests queued in thread pools (due to BK server bottlenecks). When KOP cancels these writes, the cancellation doesn't propagate to BK client. Without this, we cannot fast failure in this case. -- 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]
