You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2018/04/30 18:27:00 UTC
[jira] [Commented] (HADOOP-15430) hadoop fs -mkdir -p
path-ending-with-slash/ fails with s3guard
[ https://issues.apache.org/jira/browse/HADOOP-15430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16458834#comment-16458834 ]
Steve Loughran commented on HADOOP-15430:
-----------------------------------------
log (but not full stack). We have some tests for this at the FS level; maybe the shell is doing something
{code}
18/04/30 18:16:56 DEBUG s3a.S3AFileSystem: Getting path status for s3a://bucket/terasort/output/3 (qe/terasort/output/3)
18/04/30 18:16:56 DEBUG s3guard.DynamoDBMetadataStore: Get from table hwdev-steve-new in region us-west-1: s3a://bucket/terasort/output/3
18/04/30 18:16:56 DEBUG s3guard.DynamoDBMetadataStore: Get from table hwdev-steve-new in region us-west-1 returning for s3a://bucket/terasort/output/3: null
18/04/30 18:16:56 DEBUG s3a.S3AStorageStatistics: object_metadata_requests += 1 -> 1
18/04/30 18:16:56 DEBUG s3a.S3AStorageStatistics: object_metadata_requests += 1 -> 2
18/04/30 18:16:56 DEBUG s3a.S3AStorageStatistics: object_list_requests += 1 -> 1
18/04/30 18:16:56 DEBUG s3a.S3AFileSystem: Not Found: s3a://bucket/terasort/output/3
18/04/30 18:16:56 DEBUG s3a.S3AStorageStatistics: op_exists += 1 -> 1
18/04/30 18:16:56 DEBUG s3a.S3AStorageStatistics: op_get_file_status += 1 -> 2
18/04/30 18:16:56 DEBUG s3a.S3AFileSystem: Getting path status for s3a://bucket/terasort/output (qe/terasort/output)
18/04/30 18:16:56 DEBUG s3guard.DynamoDBMetadataStore: Get from table hwdev-steve-new in region us-west-1: s3a://bucket/terasort/output
18/04/30 18:16:57 DEBUG s3guard.DynamoDBMetadataStore: Get from table hwdev-steve-new in region us-west-1 returning for s3a://bucket/terasort/output: PathMetadata{fileStatus=FileStatus{path=s3a://bucket/terasort/output; isDirectory=true; modification_time=1525112217001; access_time=0; owner=hrt_qa; group=hrt_qa; permission=rwxrwxrwx; isSymlink=false; hasAcl=false; isEncrypted=false; isErasureCoded=false}; isEmptyDirectory=UNKNOWN; isDeleted=false}
18/04/30 18:16:57 DEBUG s3a.S3AFileSystem: Making directory: s3a://bucket/terasort/output/3/
18/04/30 18:16:57 DEBUG s3a.S3AStorageStatistics: op_mkdirs += 1 -> 1
18/04/30 18:16:57 DEBUG s3a.S3AStorageStatistics: op_get_file_status += 1 -> 3
18/04/30 18:16:57 DEBUG s3a.S3AFileSystem: Getting path status for s3a://bucket/terasort/output/3/ (qe/terasort/output/3/)
18/04/30 18:16:57 DEBUG s3guard.DynamoDBMetadataStore: Get from table hwdev-steve-new in region us-west-1: s3a://bucket/terasort/output/3/
mkdir: get on s3a://bucket/terasort/output/3/: com.amazonaws.services.dynamodbv2.model.AmazonDynamoDBException: One or more parameter values were invalid: An AttributeValue may not contain an empty string (Service: AmazonDynamoDBv2; Status Code: 400; Error Code: ValidationException; Request ID: 6M9S1ALKKSJ5AJV5A9EKDPROFBVV4KQNSO5AEMVJF66Q9ASUAAJG): One or more parameter values were invalid: An AttributeValue may not contain an empty string (Service: AmazonDynamoDBv2; Status Code: 400; Error Code: ValidationException; Request ID: 6M9S1ALKKSJ5AJV5A9EKDPROFBVV4KQNSO5AEMVJF66Q9ASUAAJG)
18/04/30 18:16:57 DEBUG s3a.S3AFileSystem: Filesystem s3a://hwdev-steve-new is closed
{code}
> hadoop fs -mkdir -p path-ending-with-slash/ fails with s3guard
> --------------------------------------------------------------
>
> Key: HADOOP-15430
> URL: https://issues.apache.org/jira/browse/HADOOP-15430
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.1.0
> Reporter: Steve Loughran
> Priority: Blocker
>
> if you call {{hadoop fs -mkdir -p path/}} on the command line with a path ending in "/:. you get a DDB error "An AttributeValue may not contain an empty string"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org