Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-15619 Über-JIRA: S3Guard Phase IV: Hadoop 3.3 features
  3. HADOOP-14576

s3guard DynamoDB resource not found: tables not ACTIVE state after initial connection

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Duplicate
    • 3.0.0-beta1
    • None
    • fs/s3
    • None

    Description

      We currently only anticipate tables not being in the ACTIVE state when first connecting. It is possible for a table to be in the ACTIVE state and move to an UPDATING state during partitioning events. Attempts to read or write during that time will result in an AmazonServerException getting thrown. We should try to handle that better...

      Attachments

        Issue Links

          duplicates

          Sub-task - The sub-task of the issue HADOOP-15837 DynamoDB table Update can fail S3A FS init

          • Major - Major loss of function.
          • Resolved
          is blocked by

          Sub-task - The sub-task of the issue HADOOP-13761 S3Guard: implement retries for DDB failures and throttling; translate exceptions

          • Blocker - Blocks development and/or testing work, production could not run
          • Resolved
          is depended upon by

          Sub-task - The sub-task of the issue HADOOP-14936 S3Guard: remove "experimental" from documentation

          • Major - Major loss of function.
          • Resolved
          relates to

          Sub-task - The sub-task of the issue HADOOP-15837 DynamoDB table Update can fail S3A FS init

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              mackrorysd Sean Mackrory
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: