- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
AWS Access Key ID and Secret Access Key must be specified as the username or password (respectively)
- Labels:
-
Cloudera Hue
-
Cloudera Manager
Created on 08-14-2013 05:43 AM - edited 09-16-2022 01:46 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My input path in another instance of EC2 as I specified input path as
s3n://xxx-ssss/
It is showing error as:
AWS Access Key ID and Secret Access Key must be specified as the username or password (respectively) of a s3n URL, or by setting the fs.s3n.awsAccessKeyId or fs.s3n.awsSecretAccessKey properties (respectively).
Where could I configure the properties for fs.s3n.awsAccessKeyId and fs.s3n.awsSecretAccessKey in cloudera manager in web UI (HUE).
Created 08-18-2013 01:38 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
For adding these properties cluster-wide into Cloudera Manager, head to CM -> HDFS -> Configuration (View and Edit) -> Search for keyword "core-site.xml safety valve" -> Edit the appropriate field by adding a list of your desired <property>…</property> configuration XML -> Save Changes. After saving, restart the cluster to propagate to all services, and also click CM -> (Cluster) Actions -> Deploy Client Configuration.
Created 08-14-2013 07:20 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Configure fs.s3n.awsAccessKeyId and fs.s3n.awsSecretAccessKey in core-site.xml.
Created 08-18-2013 01:38 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
For adding these properties cluster-wide into Cloudera Manager, head to CM -> HDFS -> Configuration (View and Edit) -> Search for keyword "core-site.xml safety valve" -> Edit the appropriate field by adding a list of your desired <property>…</property> configuration XML -> Save Changes. After saving, restart the cluster to propagate to all services, and also click CM -> (Cluster) Actions -> Deploy Client Configuration.
Created 09-05-2013 06:28 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Harsh,
I would think that the right order would be to "Deploy Client Configuration" first and then restart HDFS. Am I wrong?
Created 09-09-2013 06:57 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@herdrick: no it's actually just fine to do it in the order Harsh mentioned. CM will automatically deploy the configurations you specify on the Configuration tab of a service to that service's roles when you restart the service. For example, if you modify a datanode specific property in CM, save the change and restart the service, then all the datanodes will get new copies of their hdfs-site.xml files upon startup. The only reason to deploy the client configs that Harsh mentioned is for external client apps that want to utilize the cluster. If you made changes that will affect the behavior of clients, then the client configs need to be re-deployed. This can happen after the services are restarted, but before you attempt to reconnect to the cluster with your client app. I hope that clears it up.
Clint
