[
https://issues.apache.org/jira/browse/HDDS-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798687#comment-16798687
]
Siddharth Wagle commented on HDDS-1234:
---------------------------------------
[~linyiqun] The count is actually not significant for the API. The idea was to
actually to store the count of keys to get an estimate of how many keys would
be read using the read-only iterator on the OM's RocksDB.
The main idea is to be able to use a *prefix iterator* on the (ContainerId,
keyPrefix) -> (Key count), for efficient lookup based on ContainerId.
We probably did miss this point in the design doc; but a Container can have
millions of keys and so a storage model like this with prefix iterator, we
think will work well. The value is effectively a placeholder. [~avijayan]
Please add if I missed anything.
> Iterate the OM DB snapshot and populate the recon container DB.
> ----------------------------------------------------------------
>
> Key: HDDS-1234
> URL: https://issues.apache.org/jira/browse/HDDS-1234
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Components: Ozone Recon
> Reporter: Aravindan Vijayan
> Assignee: Aravindan Vijayan
> Priority: Major
> Fix For: 0.5.0
>
> Attachments: HDDS-1234-000.patch, HDDS-1234-001.patch,
> HDDS-1234-002.patch, HDDS-1234-003.patch
>
>
> * OM DB snapshot contains the Key->ContainerId + BlockId information.
> * Iterate the OM snapshot DB and create the reverse map of (ContainerId, Key
> prefix) -> Key count to be stored in the Recon container DB.
> * Use a codec to store data into Recon container DB.
--
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
