You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Arpit Agarwal (JIRA)" <ji...@apache.org> on 2018/10/22 22:49:00 UTC
[jira] [Created] (HDDS-710) Make Block Commit Sequence (BCS) opaque
to clients
Arpit Agarwal created HDDS-710:
----------------------------------
Summary: 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
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