You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Arpit Agarwal (Jira)" <ji...@apache.org> on 2024/06/21 23:15:00 UTC

[jira] [Commented] (HDDS-10866) HTTPFS recursive volume delete fails

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

Arpit Agarwal commented on HDDS-10866:
--------------------------------------

[~zitadombi] is this issue still relevant after HDDS-9262?

> HTTPFS recursive volume delete fails 
> -------------------------------------
>
>                 Key: HDDS-10866
>                 URL: https://issues.apache.org/jira/browse/HDDS-10866
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: HttpFS GateWay
>            Reporter: Pratyush Bhatt
>            Priority: Major
>
> I created a volume and a bucket inside it, and tried deleting the volume with HTTPFS with recursive set. But the command fails with _"Recursive volume delete using ofs is not supported"_
> {code:java}
> ozone fs -mkdir -p ofs://ozone1712905605/httpfs-vol/buck
> 24/05/16 19:21:18 INFO protocolPB.OmTransportFactory: Loading OM transport implementation org.apache.hadoop.ozone.om.protocolPB.Hadoop3OmTransportFactory as specified by configuration.
> 24/05/16 19:21:19 INFO client.ClientTrustManager: Loading certificates for client.
> 24/05/16 19:21:19 INFO rpc.RpcClient: Creating Volume: httpfs-vol, with om as owner and space quota set to -1 bytes, counts quota set to -1
> 24/05/16 19:21:19 INFO rpc.RpcClient: Creating Bucket: httpfs-vol/buck, with bucket layout FILE_SYSTEM_OPTIMIZED, om as owner, Versioning false, Storage Type set to DISK and Encryption set to false, Replication Type set to server-side default replication type, Namespace Quota set to -1, Space Quota set to -1 
> curl -i --negotiate --cacert auto-global_cacerts.pem -u : -X DELETE "https://vc0121.xyz.com:1234/webhdfs/v1/httpfs-vol?user.name=hdfs&op=DELETE&recursive=true"
> HTTP/1.1 401 Authentication required
> Pragma: no-cache
> Strict_Transport_Security: max-age=0; includeSubDomains
> X-Content-Type-Options: nosniff
> X-XSS-Protection: 1; mode=block
> WWW-Authenticate: Negotiate
> Set-Cookie: hadoop.auth=; Path=/; Secure; HttpOnly
> Content-Length: 0HTTP/1.1 500 Internal Server Error
> Date: Fri, 17 May 2024 02:33:30 GMT
> Cache-Control: no-cache
> Expires: Fri, 17 May 2024 02:33:30 GMT
> Date: Fri, 17 May 2024 02:33:30 GMT
> Pragma: no-cache
> Content-Type: application/json
> Strict_Transport_Security: max-age=0; includeSubDomains
> X-Content-Type-Options: nosniff
> X-XSS-Protection: 1; mode=block
> WWW-Authenticate: Negotiate XYZ
> Set-Cookie: hadoop.auth="u=om&p=om@EXAMPLE.COM&t=kerberos-dt&e=1715949210513&s=123"; Path=/; Secure; HttpOnly
> Transfer-Encoding: chunked{"RemoteException":{"message":"Recursive volume delete using ofs is not supported. Instead use 'ozone sh volume delete -r -id <OM_SERVICE_ID> <Volume_URI>' command","exception":"IOException","javaClassName":"java.io.IOException"}}{code}
> The behavior to delete volume recursively was done via HDDS-9262
> Do we want to keep the same behavior for HTTPFS as well? 
> cc: [~zitadombi] 
>  



--
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