[
https://issues.apache.org/jira/browse/HDDS-5094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337153#comment-17337153
]
Rakesh Radhakrishnan commented on HDDS-5094:
--------------------------------------------
Thanks a lot [~elek] for raising this issue and for the detailed patch reviews.
I've updated the jira subject line to be in sync with the proposed patch fix
and I've raised a separate Jira HDDS-5172 to handle the existing keys(Simple)
with a different cluster layout(Prefix). I hope this is fine with you.
> [FSO] Fail OM startup when turn on prefix layout with old buckets
> -----------------------------------------------------------------
>
> Key: HDDS-5094
> URL: https://issues.apache.org/jira/browse/HDDS-5094
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Marton Elek
> Assignee: Rakesh Radhakrishnan
> Priority: Major
> Labels: pull-request-available
>
> Steps to reproduce:
> 1. cd compose/upgrade && docker-compose up -d (if it fails, fix the
> permission of the dirs, and repeat the up command)
> 2. create /vol1/bucket1/dir1/dir2/key1
> 3. list the keys in /vol1/bucket1
> 4. stop the cluster
> 5. modify the docker-config by enabling prefix layout:
> {code:java}
> OZONE-SITE.XML_ozone.om.enable.filesystem.paths=true
> OZONE-SITE.XML_ozone.om.metadata.layout=prefix
> {code}
> 6. start the cluster
> Expected behavior: Fail to start OM as the configured cluster layout and
> persisted bucket layout mismatches. Presently, there is no validation during
> OM startup.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
