[ 
https://issues.apache.org/jira/browse/HDDS-5664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17442561#comment-17442561
 ] 

Rakesh Radhakrishnan edited comment on HDDS-5664 at 11/12/21, 3:34 AM:
-----------------------------------------------------------------------

[~zhengchenyu] since basic sub-tasks are in and multiple buckets with any 
layout can co-exists in a single OM, now. I'd like to take this ahead to 
completion. Kindly update the PR. Thanks again!


was (Author: rakeshr):
[~zhengchenyu] since major sub-tasks are in, I'd like to take this ahead to 
completion. Kindly update the PR. Thanks again!

> [FSO] Allow existing/old buckets with any layout during OM startup
> ------------------------------------------------------------------
>
>                 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.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to