Kirill Sizov created HDDS-9117:
----------------------------------
Summary: Bucket replication type is ignored when uploading files
through S3G
Key: HDDS-9117
URL: https://issues.apache.org/jira/browse/HDDS-9117
Project: Apache Ozone
Issue Type: Bug
Components: S3
Affects Versions: 1.4.0
Reporter: Kirill Sizov
I followed the doc page https://ozone.apache.org/docs/1.3.0/interface/s3.html
to create a bucket and exposed it to S3 via linking.
The bucket was set to have EC replication RS-3-2-1024k,
{noformat}
$ ozone sh bucket info myvol/mybucket
...
"replicationConfig" : {
"data" : 3,
"parity" : 2,
"ecChunkSize" : 1048576,
"codec" : "RS",
"replicationType" : "EC",
"requiredNodes" : 5
},
...
{noformat}
Then I tried uploading both a small file and a large file to follow a simple
and a multipart paths. Both files were uploaded with {{aws s3 cp}} command.
And here what I got:
{noformat}
$ ozone sh key info myvol/mybucket/mykey
{
"volumeName" : "myvol",
"bucketName" : "mybucket",
"name" : "mykey",
"dataSize" : 200,
"creationTime" : "2023-08-02T09:37:13.274Z",
"modificationTime" : "2023-08-02T09:37:13.313Z",
"replicationConfig" : {
"replicationFactor" : "THREE",
"requiredNodes" : 3,
"replicationType" : "RATIS"
},
"metadata" : { },
"ozoneKeyLocations" : [ {
"containerID" : 1423,
"localID" : 111677748019503057,
"length" : 200,
"offset" : 0,
"keyOffset" : 0
} ],
"file" : true
}
{noformat}
After a short investigation I found that the small file had mismatching
replication type because the linked bucket does not copy the original bucket
replication type.
And the multipart path in S3G simply ignores replication type.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
