rakeshadr commented on pull request #2151:
URL: https://github.com/apache/ozone/pull/2151#issuecomment-822383860
> I can confirm that I can create buckets where PREFIX is enabled but
`filesystem.paths` is not:
>
> ```
> bash-4.2$ ozone sh volume create /vol1
> bash-4.2$ ozone sh bucket create /vol1/bucket1
> bash-4.2$ ozone sh bucket info /vol1/bucket1
> {
> "metadata" : {
> "ozone.om.metadata.layout" : "PREFIX",
> "ozone.om.enable.filesystem.paths" : "false"
> },
> "volumeName" : "vol1",
> "name" : "bucket1",
> "storageType" : "DISK",
> "versioning" : false,
> "usedBytes" : 0,
> "usedNamespace" : 0,
> "creationTime" : "2021-04-19T10:06:25.059Z",
> "modificationTime" : "2021-04-19T10:06:25.059Z",
> "encryptionKeyName" : null,
> "sourceVolume" : null,
> "sourceBucket" : null,
> "quotaInBytes" : -1,
> "quotaInNamespace" : -1
> }
> bash-4.2$ cat /etc/hadoop/ozone-site.xml | grep paths
> bash-4.2$ cat /etc/hadoop/ozone-site.xml | grep layout
>
<property><name>ozone.om.metadata.layout</name><value>PREFIX</value></property>
> bash-4.2$
> ```
>
> If it's a supported case we need to improve the validation of this patch.
If it's not, we should open a a new issue for validation and deny this
mis-configuration as it can cause problems.
Thanks for the confirmation @elek with a test case. Instead of failing with
an error, presently OM proceeds silently with default metadata layout by making
isBucketFSOptimized flag to false. I agree to fail the startup and make it
visible to everyone. I will include this check along with this OM start up
validation patch.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
