You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Rishabh Patel (Jira)" <ji...@apache.org> on 2025/11/05 00:13:00 UTC
[jira] [Updated] (HDDS-13884) Populate block file metadata with helper fields
[ https://issues.apache.org/jira/browse/HDDS-13884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rishabh Patel updated HDDS-13884:
---------------------------------
Description:
The block file supports storing arbitrary metadata.
Saving the following fields can help with debugging and improve the visibility into the system.
* volume/bucket/key name
* parentId/objectId
* Original key creation timestamp
Storing such information can help answer questions about any arbitrary block file such as
* For which key was this block file created?
* Regardless of replication/ EC reconstruction/OS filesystem timestamps , when was this block file originally created for the very first time?
Today these questions can be answered only if the chain of metadata from OM to Datanodes is intact.
was:
The block file supports storing arbitrary metadata.
Saving the following fields can help with debugging and improve the visibility into the system.
* Volume/Bucket/Key name
* parentId/objectId
* Original key creation timestamp
Storing such information can help answer questions about any arbitrary block file such as
* For which key was this block file created?
* Regardless of replication/ EC reconstruction/OS filesystem timestamps , when was this block file originally created for the very first time?
Today these questions can be answered only if the chain of metadata from OM to Datanodes is intact.
> Populate block file metadata with helper fields
> -----------------------------------------------
>
> Key: HDDS-13884
> URL: https://issues.apache.org/jira/browse/HDDS-13884
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Rishabh Patel
> Assignee: Rishabh Patel
> Priority: Major
>
> The block file supports storing arbitrary metadata.
> Saving the following fields can help with debugging and improve the visibility into the system.
> * volume/bucket/key name
> * parentId/objectId
> * Original key creation timestamp
>
> Storing such information can help answer questions about any arbitrary block file such as
> * For which key was this block file created?
> * Regardless of replication/ EC reconstruction/OS filesystem timestamps , when was this block file originally created for the very first time?
> Today these questions can be answered only if the chain of metadata from OM to Datanodes is intact.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org