You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Rakesh Radhakrishnan (Jira)" <ji...@apache.org> on 2021/08/26 06:01:00 UTC
[jira] [Commented] (HDDS-5664) [FSO] Ignore validate bucket layout
since bucket layout supported in HDDS-5362.
[ https://issues.apache.org/jira/browse/HDDS-5664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404969#comment-17404969 ]
Rakesh Radhakrishnan commented on HDDS-5664:
--------------------------------------------
Thanks [~zhengchenyu] for working on this. I have moved this to a sub-task of HDDS-5672 as bucket layout feature realization requires some more changes.
> [FSO] Ignore validate bucket layout since bucket layout supported in HDDS-5362.
> -------------------------------------------------------------------------------
>
> Key: HDDS-5664
> URL: https://issues.apache.org/jira/browse/HDDS-5664
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: zhengchenyu
> Assignee: zhengchenyu
> Priority: Major
> Labels: pull-request-available
>
> I have a ozone cluster, prefix is enable when setup cluster. when restart om, then error below:
> {code}
> java.io.IOException: Failed to start OM in PREFIX layout format as existing bucket has a different layout SIMPLE metadata format
> {code}
> This issue is similar to HDDS-5094. Later in HDDS-5362, bucket layout is supported, then addFSOptimizedBucketDetails is removed in this https://github.com/apache/ozone/commit/7df192530810a07d3b976c3a56c46328c0b1d591. So om crash when restart if layout is PREFIX.
> I think there is no need to validate bucket type since HDDS-5362.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org