[ 
https://issues.apache.org/jira/browse/HDDS-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17482968#comment-17482968
 ] 

Attila Doroszlai commented on HDDS-6223:
----------------------------------------

[~rakeshr], please note that:

# Even old client itself may create FSO bucket and populate it if default 
layout is FSO
# Old client can read the keys, just cannot list them (like a Unix directory 
with chmod 711)
# List via Ozone FS works (I think it uses listStatus internally)

> Ozone 1.1.0 client listKeys on FSO bucket returns empty list
> ------------------------------------------------------------
>
>                 Key: HDDS-6223
>                 URL: https://issues.apache.org/jira/browse/HDDS-6223
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: Ozone Client, Ozone Manager
>    Affects Versions: 1.3.0
>            Reporter: Attila Doroszlai
>            Assignee: Rakesh Radhakrishnan
>            Priority: Critical
>
> Ozone 1.1.0 or earlier client gets empty list for listKeys operation on FSO 
> bucket in 1.3.0 cluster.
> {code:title=setup}
> $ cd hadoop-ozone/dist/target/ozone-1.3.0-SNAPSHOT/compose/xcompat
> $ export COMPOSE_FILE=new-cluster.yaml:clients.yaml
> $ docker-compose up -d --scale datanode=3
> $ docker-compose exec new_client bash
> bash-4.2$ ozone freon ockg -n1 -t1 -p test
> bash-4.2$ ozone sh bucket info /vol1/bucket1
> {
>   "metadata" : { },
>   "volumeName" : "vol1",
>   "name" : "bucket1",
>   "storageType" : "DISK",
>   "versioning" : false,
>   "usedBytes" : 805306368,
>   "usedNamespace" : 1,
>   "creationTime" : "2022-01-25T18:02:35.564Z",
>   "modificationTime" : "2022-01-25T18:02:35.564Z",
>   "quotaInBytes" : -1,
>   "quotaInNamespace" : -1,
>   "bucketLayout" : "FILE_SYSTEM_OPTIMIZED",
>   "owner" : "hadoop",
>   "link" : false
> }
> bash-4.2$ ozone sh key list /vol1/bucket1
> [ {
>   "volumeName" : "vol1",
>   "bucketName" : "bucket1",
>   "name" : "test/",
>   "dataSize" : 0,
>   "creationTime" : "2022-01-25T18:02:35.765Z",
>   "modificationTime" : "2022-01-25T18:02:35.765Z",
>   "replicationConfig" : {
>     "replicationFactor" : "ONE",
>     "requiredNodes" : 1,
>     "replicationType" : "RATIS"
>   },
>   "replicationType" : "RATIS",
>   "replicationFactor" : 1
> }, {
>   "volumeName" : "vol1",
>   "bucketName" : "bucket1",
>   "name" : "test/0",
>   "dataSize" : 10240,
>   "creationTime" : "2022-01-25T18:02:35.765Z",
>   "modificationTime" : "2022-01-25T18:02:38.545Z",
>   "replicationConfig" : {
>     "replicationFactor" : "THREE",
>     "requiredNodes" : 3,
>     "replicationType" : "RATIS"
>   },
>   "replicationType" : "RATIS",
>   "replicationFactor" : 3
> } ]
> {code}
> {code:title=repro}
> $ docker-compose exec old_client_1_0_0 ozone sh --verbose key list 
> /vol1/bucket1
> Volume Name : vol1
> Bucket Name : bucket1
> Found : 0 keys for bucket bucket1 in volume : vol1
> {code}
> Same happens with 1.1.0 client.  1.2.0+ client works fine.  (These newer 
> versions are being added in HDDS-6221.)
> Also, 1.1.0 client works fine if bucket layout is OBJECT_STORE.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to