[
https://issues.apache.org/jira/browse/HDFS-12735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241004#comment-16241004
]
Anu Engineer commented on HDFS-12735:
-------------------------------------
{code}
return CompletableFuture
.supplyAsync(() -> f.apply(dispatcher.dispatch(request)),
threadPoolExecutor);
{code}
Just a question to make sure that this code does not introduce a race
condition. Could you please help me understand what happens if the following
scenario?
1. We write a chunk
2. We delete that same chunk immediately.
In my mind, it is quite possible that these actions can race. Can you please
help me understand how the ordering is maintained?
> Make ContainerStateMachine#applyTransaction async
> -------------------------------------------------
>
> Key: HDFS-12735
> URL: https://issues.apache.org/jira/browse/HDFS-12735
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Lokesh Jain
> Assignee: Lokesh Jain
> Labels: performance
> Attachments: HDFS-12735-HDFS-7240.000.patch,
> HDFS-12735-HDFS-7240.001.patch
>
>
> Currently ContainerStateMachine#applyTransaction makes a synchronous call to
> dispatch client requests. Idea is to have a thread pool which dispatches
> client requests and returns a CompletableFuture.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
