hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anu Engineer (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDDS-710) Make Block Commit Sequence (BCS) opaque to clients
Date Thu, 28 Feb 2019 22:13:00 GMT

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

Anu Engineer updated HDDS-710:
------------------------------
    Sprint: HDDS BadLands

> Make Block Commit Sequence (BCS) opaque to clients
> --------------------------------------------------
>
>                 Key: HDDS-710
>                 URL: https://issues.apache.org/jira/browse/HDDS-710
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>          Components: Ozone Client
>            Reporter: Arpit Agarwal
>            Assignee: Arpit Agarwal
>            Priority: Critical
>
> An immutable block is identified by the following:
> - Container ID
> - Local Block ID
> - BCS (Block Commit Sequence ID)
> All of these values are currently exposed to the client. Instead we can have a composite
block ID that hides these details from the client. A first thought is a naive implementation
that generates a 192-bit (3x64-bit) block ID.
> Proposed by [~anu] in HDDS-676.



--
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