[
https://issues.apache.org/jira/browse/HDFS-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jian Zhang updated HDFS-17552:
------------------------------
Description:
h3. Description
In the implementation of asynchronous Rpc.client, the main methods used include
HADOOP-13226, HDFS-10224, etc.
However, the existing implementation does not support `CompletableFuture`;
instead, it relies on setting up callbacks, which can lead to the "callback
hell" problem. Using `CompletableFuture` can better organize asynchronous
callbacks. Therefore, on the basis of the existing implementation, by using
`CompletableFuture`, once the `client.call` is completed, the asynchronous
thread handles the response of this call without blocking the main thread.
*Test*
new UT TestAsyncIPC#testAsyncCallWithCompletableFuture()
was:
h3. Description
In the implementation of asynchronous Rpc.client, the main methods used include
HADOOP-13226, HDFS-10224, etc.
However, the existing implementation does not support `CompletableFuture`;
instead, it relies on setting up callbacks, which can lead to the "callback
hell" problem. Using `CompletableFuture` can better organize asynchronous
callbacks. Therefore, on the basis of the existing implementation, by using
`CompletableFuture`, once the `client.call` is completed, the asynchronous
thread handles the response of this call without blocking the main thread.
*Test*
new UT ** TestAsyncIPC#testAsyncCallWithCompletableFuture()
> [ARR] RPC client uses CompletableFuture to support asynchronous operations.
> ---------------------------------------------------------------------------
>
> Key: HDFS-17552
> URL: https://issues.apache.org/jira/browse/HDFS-17552
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Jian Zhang
> Assignee: Jian Zhang
> Priority: Major
>
> h3. Description
> In the implementation of asynchronous Rpc.client, the main methods used
> include HADOOP-13226, HDFS-10224, etc.
> However, the existing implementation does not support `CompletableFuture`;
> instead, it relies on setting up callbacks, which can lead to the "callback
> hell" problem. Using `CompletableFuture` can better organize asynchronous
> callbacks. Therefore, on the basis of the existing implementation, by using
> `CompletableFuture`, once the `client.call` is completed, the asynchronous
> thread handles the response of this call without blocking the main thread.
>
> *Test*
> new UT TestAsyncIPC#testAsyncCallWithCompletableFuture()
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
