hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shashikant Banerjee (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDDS-550) Serialize ApplyTransaction calls per Container in ContainerStateMachine
Date Thu, 11 Oct 2018 18:21:00 GMT

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

Shashikant Banerjee updated HDDS-550:
    Attachment:     (was: HDDS-550.008.patch)

> Serialize ApplyTransaction calls per Container in ContainerStateMachine
> -----------------------------------------------------------------------
>                 Key: HDDS-550
>                 URL: https://issues.apache.org/jira/browse/HDDS-550
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Shashikant Banerjee
>            Assignee: Shashikant Banerjee
>            Priority: Major
>         Attachments: HDDS-550.001.patch, HDDS-550.002.patch, HDDS-550.003.patch, HDDS-550.004.patch,
HDDS-550.005.patch, HDDS-550.006.patch, HDDS-550.007.patch, HDDS-550.008.patch
> As part of handling Node failures in Ozone, the block commit need to happen in order
inside ContainerStateMachine per container. With RATIS-341, it is guaranteed that the 
applyTransaction calls for committing the write chunks will be initiated only when the WriteStateMachine
data for write Chunk operations finish. 
> This Jira is aimed at making all the applyTransaction operations inside ContainerStateMachine
serial per container with a single thread Executor per container handling all applyTransactions

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message