[
https://issues.apache.org/jira/browse/HDDS-5094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17319502#comment-17319502
]
Rakesh Radhakrishnan commented on HDDS-5094:
--------------------------------------------
[~elek], IMHO to disallow the startup if it contains old bucket layout format
and I posted a patch to fail the startup. This means that the new feature is
allowed only in a fresh new cluster. Later, I agree to support this case,
existing old key(s) should be visible in prefix based OM layout.
> [FSO] Existing keys become unavailable after turning on prefix layout
> ---------------------------------------------------------------------
>
> 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}
> OZONE-SITE.XML_ozone.om.enable.filesystem.paths=true
> OZONE-SITE.XML_ozone.om.metadata.layout=prefix
> {code}
> 6. start the cluster
> 7. list the keys in /vol1/bucket1 --> it returns with empty result
> Expected behavior: the old keys supposed to be available
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
