You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/09/30 05:38:00 UTC
[jira] [Updated] (HDDS-13066) Better error code and message - bucket link points to non-existent volume
[ https://issues.apache.org/jira/browse/HDDS-13066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HDDS-13066:
----------------------------------
Labels: pull-request-available (was: )
> Better error code and message - bucket link points to non-existent volume
> -------------------------------------------------------------------------
>
> Key: HDDS-13066
> URL: https://issues.apache.org/jira/browse/HDDS-13066
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: István Fajth
> Assignee: rajesh
> Priority: Major
> Labels: pull-request-available
>
> Consider the case, when someone links to a bucket, which does not exists. As links does not necessarily point to an existing location, this is fine, and this may also be fine in case the linked bucket is removed but the link remains in the system.
> In Ozone it is also possible to link to a non-existent bucket on a non-existent volume, the base principle still stands, linking to a non-existent thing in a non-existent thing is essentially linking to something that does not exists.
> In this latter scenario however, operations on the linked bucket results in a VOLUME_NOT_FOUND, as we run into this error during resolving the link and trying to do the operation on the source bucket, which is on a volume that does not exists.
> We should be able to do better than this, and provide a proper error message that says the linked bucket does not exists.
--
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