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 2019/06/25 16:19:00 UTC
[jira] [Commented] (HADOOP-16393) S3Guard init command uses global
settings, not those of target bucket
[ https://issues.apache.org/jira/browse/HADOOP-16393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16872491#comment-16872491 ]
Steve Loughran commented on HADOOP-16393:
-----------------------------------------
but you can't actually create the bucket because the init command picks up the global one
{code}
bin/hadoop s3guard init s3a://hwdev-steve-london/
2019-06-25 17:18:07,075 [main] DEBUG s3guard.S3GuardTool (S3GuardTool.java:run(1623)) - Executing command init
2019-06-25 17:18:07,140 [main] DEBUG s3a.S3AUtils (S3AUtils.java:createAWSCredentialProvider(710)) - Credential provider class is org.apache.hadoop.fs.s3a.TemporaryAWSCredentialsProvider
2019-06-25 17:18:07,140 [main] DEBUG s3a.S3AUtils (S3AUtils.java:createAWSCredentialProvider(710)) - Credential provider class is org.apache.hadoop.fs.s3a.SimpleAWSCredentialsProvider
2019-06-25 17:18:07,146 [main] DEBUG s3a.S3AUtils (S3AUtils.java:createAWSCredentialProvider(710)) - Credential provider class is com.amazonaws.auth.EnvironmentVariableCredentialsProvider
2019-06-25 17:18:07,146 [main] DEBUG s3a.S3AUtils (S3AUtils.java:createAWSCredentialProvider(710)) - Credential provider class is org.apache.hadoop.fs.s3a.auth.IAMInstanceCredentialsProvider
2019-06-25 17:18:07,146 [main] DEBUG s3a.S3AUtils (S3AUtils.java:createAWSCredentialProviderSet(609)) - For URI null, using credentials AWSCredentialProviderList[refcount= 1: [TemporaryAWSCredentialsProvider, SimpleAWSCredentialsProvider, EnvironmentVariableCredentialsProvider, org.apache.hadoop.fs.s3a.auth.IAMInstanceCredentialsProvider@e874448]
2019-06-25 17:18:07,148 [main] DEBUG s3guard.DynamoDBMetadataStore (DynamoDBMetadataStore.java:createDynamoDB(367)) - Creating DynamoDB client class org.apache.hadoop.fs.s3a.s3guard.DynamoDBClientFactory$DefaultDynamoDBClientFactory with S3 region eu-west-1
2019-06-25 17:18:07,439 [main] DEBUG s3a.S3AUtils (S3AUtils.java:intOption(979)) - Value of fs.s3a.connection.maximum is 48
2019-06-25 17:18:07,440 [main] DEBUG s3a.S3AUtils (S3AUtils.java:intOption(979)) - Value of fs.s3a.attempts.maximum is 8
2019-06-25 17:18:07,440 [main] DEBUG s3a.S3AUtils (S3AUtils.java:intOption(979)) - Value of fs.s3a.connection.establish.timeout is 5000
2019-06-25 17:18:07,440 [main] DEBUG s3a.S3AUtils (S3AUtils.java:intOption(979)) - Value of fs.s3a.connection.timeout is 5000
2019-06-25 17:18:07,440 [main] DEBUG s3a.S3AUtils (S3AUtils.java:intOption(979)) - Value of fs.s3a.socket.send.buffer is 65536
2019-06-25 17:18:07,441 [main] DEBUG s3a.S3AUtils (S3AUtils.java:intOption(979)) - Value of fs.s3a.socket.recv.buffer is 32678
2019-06-25 17:18:07,443 [main] DEBUG s3a.S3AUtils (S3AUtils.java:initUserAgent(1323)) - Using User-Agent: Hadoop 3.1.1.7.0.0.0-SNAPSHOT
2019-06-25 17:18:07,444 [main] DEBUG s3guard.DynamoDBClientFactory (DynamoDBClientFactory.java:createDynamoDBClient(86)) - Creating DynamoDB client in region eu-west-1
2019-06-25 17:18:07,956 [main] DEBUG s3a.S3AUtils (S3AUtils.java:intOption(979)) - Value of fs.s3a.executor.capacity is 16
2019-06-25 17:18:07,956 [main] DEBUG s3a.S3AUtils (S3AUtils.java:longOption(1000)) - Value of fs.s3a.threads.keepalivetime is 60
2019-06-25 17:18:07,974 [main] DEBUG s3guard.DynamoDBMetadataStore (DynamoDBMetadataStore.java:initTable(1666)) - Binding to table hwdev-steve-ireland-new
2019-06-25 17:18:08,027 [main] DEBUG s3a.AWSCredentialProviderList (AWSCredentialProviderList.java:getCredentials(197)) - No credentials from TemporaryAWSCredentialsProvider: org.apache.hadoop.fs.s3a.auth.NoAwsCredentialsException: Session credentials in Hadoop configuration: No AWS Credentials
2019-06-25 17:18:08,028 [main] DEBUG s3a.AWSCredentialProviderList (AWSCredentialProviderList.java:getCredentials(184)) - Using credentials from SimpleAWSCredentialsProvider
2019-06-25 17:18:08,569 [main] DEBUG s3guard.DynamoDBMetadataStore (DynamoDBMetadataStore.java:initTable(1668)) - Table state: {AttributeDefinitions: [{AttributeName: child,AttributeType: S}, {AttributeName: parent,AttributeType: S}],TableName: hwdev-steve-ireland-new,KeySchema: [{AttributeName: parent,KeyType: HASH}, {AttributeName: child,KeyType: RANGE}],TableStatus: ACTIVE,CreationDateTime: Wed Jun 05 13:23:18 BST 2019,ProvisionedThroughput: {NumberOfDecreasesToday: 0,ReadCapacityUnits: 0,WriteCapacityUnits: 0},TableSizeBytes: 126729,ItemCount: 754,TableArn: arn:aws:dynamodb:eu-west-1:980678866538:table/hwdev-steve-ireland-new,TableId: b4b1b660-b301-4813-9cbd-e52350f10623,BillingModeSummary: {BillingMode: PAY_PER_REQUEST,LastUpdateToPayPerRequestDateTime: Wed Jun 05 13:32:07 BST 2019},}
2019-06-25 17:18:08,609 [main] DEBUG s3guard.DynamoDBMetadataStore (DynamoDBMetadataStore.java:initTable(1697)) - Using existing DynamoDB table hwdev-steve-ireland-new in region eu-west-1 created Wed Jun 05 13:23:28 BST 2019
2019-06-25 17:18:08,609 [main] INFO s3guard.S3GuardTool (S3GuardTool.java:initMetadataStore(320)) - Metadata store DynamoDBMetadataStore{region=eu-west-1, tableName=hwdev-steve-ireland-new, tableArn=arn:aws:dynamodb:eu-west-1:980678866538:table/hwdev-steve-ireland-new} is initialized.
Metadata Store Diagnostics:
ARN=arn:aws:dynamodb:eu-west-1:980678866538:table/hwdev-steve-ireland-new
billing-mode=per-request
description=S3Guard metadata store in DynamoDB
name=hwdev-steve-ireland-new
persist.authoritative.bit=true
read-capacity=0
region=eu-west-1
retryPolicy=ExponentialBackoffRetry(maxRetries=9, sleepTime=250 MILLISECONDS)
size=126729
status=ACTIVE
table={AttributeDefinitions: [{AttributeName: child,AttributeType: S}, {AttributeName: parent,AttributeType: S}],TableName: hwdev-steve-ireland-new,KeySchema: [{AttributeName: parent,KeyType: HASH}, {AttributeName: child,KeyType: RANGE}],TableStatus: ACTIVE,CreationDateTime: Wed Jun 05 13:23:18 BST 2019,ProvisionedThroughput: {NumberOfDecreasesToday: 0,ReadCapacityUnits: 0,WriteCapacityUnits: 0},TableSizeBytes: 126729,ItemCount: 754,TableArn: arn:aws:dynamodb:eu-west-1:980678866538:table/hwdev-steve-ireland-new,TableId: b4b1b660-b301-4813-9cbd-e52350f10623,BillingModeSummary: {BillingMode: PAY_PER_REQUEST,LastUpdateToPayPerRequestDateTime: Wed Jun 05 13:32:07 BST 2019},}
write-capacity=0
{code}
> S3Guard init command uses global settings, not those of target bucket
> ---------------------------------------------------------------------
>
> Key: HADOOP-16393
> URL: https://issues.apache.org/jira/browse/HADOOP-16393
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.2.0
> Reporter: Steve Loughran
> Priority: Major
>
> If you call {{s3guard init s3a://name/}} then the custom bucket options of fs.s3a.bucket.name are not picked up, instead the global value is used.
> Fix: take the name of the bucket and use that to eval properties and patch the config used for the init command.
--
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