You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Shashikant Banerjee (JIRA)" <ji...@apache.org> on 2018/08/17 09:10:00 UTC
[jira] [Resolved] (HDDS-244) Synchronize PutKey and WriteChunk
requests in Ratis Server
[ https://issues.apache.org/jira/browse/HDDS-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shashikant Banerjee resolved HDDS-244.
--------------------------------------
Resolution: Fixed
> Synchronize PutKey and WriteChunk requests in Ratis Server
> ----------------------------------------------------------
>
> Key: HDDS-244
> URL: https://issues.apache.org/jira/browse/HDDS-244
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Datanode
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Priority: Blocker
> Fix For: 0.2.1
>
>
> In Ratis, all the WriteChunk Requests are submitted to Ratis with Replication_Majority semantics. That means, the command execution from Ratis completes any 2 of 3 datanodes complete execution of the request. It might happen that on one of the follower, PutKey might start execution while all the WriteChunks requests processing for the same block are still in progress. There needs to be a synchronization enforced between PutKey and corresponding WriteChunk requests in the ContainerStateMachine. This Jira aims to address this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org