| Re: [DISCUSS] Optimize the invoke retry of async repsonder when
some nameservices are slow |
+ hdfs-dev.
Thanks Haobo for your proposal. As you mentioned above, this may be
related to RBF and ARR features, right?
IMO, it is necessary to improve responder performance, but I am a
little confused
+ hdfs-dev.
Thanks Haobo for your proposal. As you mentioned above, this may be
related to RBF and ARR features, right?
IMO, it is necessary to improve responder performance, but I am a
little confused about nameservice will slow
down the whole system, The first glance is client or package size
sh
think you meant to send this to hdfs-dev, not the -subscribe list.
On Wed, 16 Apr 2025 at 14:09, Zhanghaobo wrote:
> Hello, everyone, so sorry to bother you and I would like to discuss how
> to optimize the invoke retry logic of async repsonder when some
> nameservices are slow.
> Currently,
Hello, everyone, so sorry to bother you and I would like to discuss how to
optimize the invoke retry logic of async repsonder when some nameservices are
slow.
Currently, all nameservices share one async responder thread pool which is in
class AsyncRpcProtocolPBUtil.
Think below situation, we
