Ryan Blough created HDDS-12649:
----------------------------------

             Summary: Include the path that failed the check in 
'org.apache.hadoop.ozone.om.exceptions.OMException: Bucket or Volume length is 
illegal, valid length is 3-63 characters' errors?
                 Key: HDDS-12649
                 URL: https://issues.apache.org/jira/browse/HDDS-12649
             Project: Apache Ozone
          Issue Type: Improvement
          Components: Ozone Manager
    Affects Versions: 1.3.0
            Reporter: Ryan Blough


This error is frustratingly vague in most circumstances where it shows up. The 
motivating example:

- The error appeared when a distcp command fails, like so:

{{}}
{code:java}
25/03/09 12:18:54 ERROR tools.DistCp: Exception encountered
INVALID_VOLUME_NAME org.apache.hadoop.ozone.om.exceptions.OMException: Bucket 
or Volume length is illegal, valid length is 3-63 characters
at 
org.apache.hadoop.ozone.client.rpc.RpcClient.verifyVolumeName(RpcClient.java:704)
at 
org.apache.hadoop.ozone.client.rpc.RpcClient.getBucketDetails(RpcClient.java:1240){code}
{{{{}}}}
{{{{- Checking all of the volume and bucket names in Ozone, in both source and 
destination clusters: pass the check.}}}}
{{{{}}}}
{{{{- The actual source of the error was Yarn, while creating a path for 
Spark.}}}}
{{{{}}}}
{{{{- The problem was the specified name for this Spark path.}}}}
{{{{}}}}
{{{{Troubleshooting this error commonly involves checking the whole filesystem 
and/or multiple services. If the error included the path that failed the check, 
it would be trivial to immediately resolve.}}}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to