Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-14831 Über-jira: S3a phase IV: Hadoop 3.1 features
  3. HADOOP-14832

Listing s3a bucket without credentials gives Interrupted error

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Minor
    • Resolution: Cannot Reproduce
    • 3.0.0-beta1
    • None
    • fs/s3
    • None

    Description

      In trunk pseudo distributed mode, without setting s3a credentials, listing an s3a bucket only gives "Interrupted" error :

      $ hadoop fs -ls s3a://bucket/
      ls: Interrupted
      

      In comparison, branch-2 gives a much better error message:

      (branch-2)$ hadoop_env hadoop fs -ls s3a://bucket/
      ls: doesBucketExist on hdfs-cce: com.amazonaws.AmazonClientException: No AWS Credentials provided by BasicAWSCredentialsProvider EnvironmentVariableCredentialsProvider InstanceProfileCredentialsProvider : com.amazonaws.SdkClientException: Unable to load credentials from service endpoint
      

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            jzhuge John Zhuge
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment