You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Wei-Chiu Chuang (Jira)" <ji...@apache.org> on 2023/03/30 16:53:00 UTC
[jira] [Comment Edited] (HDDS-8292) Inconsistent key name handling for FSO bucket files
[ https://issues.apache.org/jira/browse/HDDS-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17706965#comment-17706965 ]
Wei-Chiu Chuang edited comment on HDDS-8292 at 3/30/23 4:52 PM:
----------------------------------------------------------------
Attached [^omdb-hdds-8292.tgz] for reference.
You can uncompress the tarball, and use the following command to open it
{noformat}
ozone debug ldb --db=om.db scan --column_family=fileTable -l -1 --with-keys|less
{noformat}
[^om-audit-hdds-8292.tgz] is the audit log files, in case it turn out to be useful.
Interestingly, the rocksdb in the leader OM and follower OMs are not consistent. The corrupt key names in leader are different from those in the follower.
was (Author: jojochuang):
Attached [^omdb-hdds-8292.tgz] for reference.
You can uncompress the tarball, and use the following command to open it
{noformat}
ozone debug ldb --db=om.db scan --column_family=fileTable -l -1 --with-keys|less
{noformat}
[^om-audit-hdds-8292.tgz] is the audit log files, in case it can be useful.
Interestingly, the rocksdb in the leader OM and follower OMs are not consistent. The corrupt key names in leader are different from those in the follower.
> Inconsistent key name handling for FSO bucket files
> ---------------------------------------------------
>
> Key: HDDS-8292
> URL: https://issues.apache.org/jira/browse/HDDS-8292
> Project: Apache Ozone
> Issue Type: Sub-task
> Affects Versions: 1.4.0
> Reporter: Wei-Chiu Chuang
> Assignee: Ashish Kumar
> Priority: Blocker
> Labels: proton
> Attachments: om-audit-hdds-8292.tgz, omdb-hdds-8292.tgz
>
>
> The definition of the field OmKeyInfo.keyName is ambiguous.
> In some of the code, it is the full path to a file; in some, it is just the final part (excluding the path).
> I am looking at a cluster where some of the entries in fileTable in its OM db has full path, and some don't.
> {noformat}
> # ozone debug ldb --db=om.db scan --column_family=fileTable -l -1 --with-keys | less
> "/-9223372036854561536/-9223372036854561024/-9223372036854525695/433dfbc470b54a0e9a23ed79240c3dc3" -> {
> "volumeName": "vol1",
> "bucketName": "bucket1",
> "keyName": "hbase/data/hbase/meta/1588230740/info/433dfbc470b54a0e9a23ed79240c3dc3",
> ...
> "/-9223372036854561536/-9223372036854561024/-9223372036854525695/c3a068821e7544caae7cdbaf9ca1b263" -> {
> "volumeName": "vol1",
> "bucketName": "bucket1",
> "keyName": "c3a068821e7544caae7cdbaf9ca1b263",
> {noformat}
> Bug: ListStatus request returns incorrect path name, because OzoneListStatusHelper.getStatus() expects the keyName to be just the final part, and prepend the prefix, which is incorrect for the example above.
--
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