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-603) Add BlockCommitSequenceId field per Container and expose it in Container Reports
Date Fri, 12 Oct 2018 09:16:00 GMT

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

Shashikant Banerjee updated HDDS-603:
-------------------------------------
    Attachment: HDDS-603.003.patch

> Add BlockCommitSequenceId field per Container and expose it in Container Reports
> --------------------------------------------------------------------------------
>
>                 Key: HDDS-603
>                 URL: https://issues.apache.org/jira/browse/HDDS-603
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Shashikant Banerjee
>            Assignee: Shashikant Banerjee
>            Priority: Major
>         Attachments: HDDS-603.000.patch, HDDS-603.001.patch, HDDS-603.002.patch, HDDS-603.003.patch
>
>
> HDDS-450 adds a blockCommitSequenceId filed per block commit in container Db. The blockCommitSequenceId
now needs to be updated per container replica and the same needs to be reported to SCM via
container reports. This Jira aims to address this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


Mime
View raw message