hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mingliang Liu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13908) S3Guard: Existing tables may not be initialized correctly in DynamoDBMetadataStore
Date Thu, 05 Jan 2017 01:49:58 GMT

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

Mingliang Liu commented on HADOOP-13908:
----------------------------------------

When disabling the parallel test, the test result (table existent and table nonexistent) is:
{code}
Results :

Tests in error:
  ITestS3AAWSCredentialsProvider.testAnonymousProvider:133 » AWSServiceIO initTa...
  ITestS3ACredentialsInURL.testInstantiateFromURL:86 » InterruptedIO initTable: ...
  ITestS3ACredentialsInURL.testInvalidCredentialsFail:127 » AccessDenied s3a://m...
  ITestS3AFileSystemContract>FileSystemContractBaseTest.testRenameToDirWithSamePrefixAllowed:669->FileSystemContractBaseTest.rename:525
» AWSServiceIO
  ITestS3ADeleteFilesOneByOne>ITestS3ADeleteManyFiles.testBulkRenameAndDelete:101 » AWSServiceIO
  ITestS3ADeleteManyFiles.testBulkRenameAndDelete:101 » AWSServiceIO move: com.a...

Tests run: 321, Failures: 0, Errors: 6, Skipped: 8
{code}
The first three are about the credentials. The last two are being fixed by [HADOOP-13934],
the {{FileSystemContractBaseTest#testRenameToDirWithSamePrefixAllowed}} is also discussed
there.

> S3Guard: Existing tables may not be initialized correctly in DynamoDBMetadataStore
> ----------------------------------------------------------------------------------
>
>                 Key: HADOOP-13908
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13908
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: HADOOP-13345
>            Reporter: Mingliang Liu
>            Assignee: Mingliang Liu
>         Attachments: HADOOP-13908-HADOOP-13345.000.patch, HADOOP-13908-HADOOP-13345.001.patch,
HADOOP-13908-HADOOP-13345.002.patch, HADOOP-13908-HADOOP-13345.002.patch, HADOOP-13908-HADOOP-13345.003.patch,
HADOOP-13908-HADOOP-13345.004.patch
>
>
> This was based on discussion in [HADOOP-13455]. Though we should not create table unless
the config {{fs.s3a.s3guard.ddb.table.create}} is set true, we still have to get the existing
table in {{DynamoDBMetadataStore#initialize()}} and wait for its becoming active, before any
table/item operations.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message