You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Christos Bisias (Jira)" <ji...@apache.org> on 2022/09/12 17:13:00 UTC
[jira] [Created] (HDDS-7217) OM logs wrong bucket layout
Christos Bisias created HDDS-7217:
-------------------------------------
Summary: OM logs wrong bucket layout
Key: HDDS-7217
URL: https://issues.apache.org/jira/browse/HDDS-7217
Project: Apache Ozone
Issue Type: Bug
Reporter: Christos Bisias
Assignee: Christos Bisias
When creating a bucket using a layout specified in ozone configuration, OM logs don't display the specified bucket layout but the Ozone default(LEGACY). The bucket info printed in the CLI, is the correct one. If a bucket layout is specified while issuing the create command, then the correct layout is logged. This was first noticed while creating an encrypted bucket but it occurs even will a non encrypted one.
*Eg.*
Specified bucket layout in ozone-site.xml is FSO
{code:java}
OZONE-SITE.XML_ozone.default.bucket.layout=FILE_SYSTEM_OPTIMIZED {code}
Create a bucket without specifying the layout and then check info.
{code:java}
bash-4.2$ ozone sh bucket create /vol/buck
bash-4.2$ ozone sh bucket info /vol/buck
{
"metadata" : { },
"volumeName" : "vol",
"name" : "buck",
"storageType" : "DISK",
"versioning" : false,
"usedBytes" : 0,
"usedNamespace" : 0,
"creationTime" : "2022-09-12T17:11:15.175Z",
"modificationTime" : "2022-09-12T17:11:15.175Z",
"quotaInBytes" : -1,
"quotaInNamespace" : -1,
"bucketLayout" : "FILE_SYSTEM_OPTIMIZED",
"owner" : "hadoop",
"link" : false
}
{code}
Check OM logs.
{code:java}
[OM StateMachine ApplyTransaction Thread - 0] INFO bucket.OMBucketCreateRequest: created bucket: buck of layout LEGACY in volume: vol
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org