[jira] [Updated] (HDDS-244) PutKey should get executed only if all WriteChunk request for the same block complete in Ratis

2018-07-10 Thread Shashikant Banerjee (JIRA)


 [ 
https://issues.apache.org/jira/browse/HDDS-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shashikant Banerjee updated HDDS-244:
-
Description: 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.  (was: 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 WriteChunkrequets in the ContainerStateMachine. This Jira aims to 
address this.)

> PutKey should get executed only if all WriteChunk request for the same block 
> complete in Ratis
> --
>
> 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: Major
> 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-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDDS-244) PutKey should get executed only if all WriteChunk request for the same block complete in Ratis

2018-07-10 Thread Shashikant Banerjee (JIRA)


 [ 
https://issues.apache.org/jira/browse/HDDS-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shashikant Banerjee updated HDDS-244:
-
Summary: PutKey should get executed only if all WriteChunk request for the 
same block complete in Ratis  (was: PutKey should get executed only if all 
WriteChunk request fior the same block complete in Ratis)

> PutKey should get executed only if all WriteChunk request for the same block 
> complete in Ratis
> --
>
> 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: Major
> 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 WriteChunkrequets 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-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org