Details

    • Type: Sub-task
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.8.0
    • Fix Version/s: None
    • Component/s: fs/s3
    • Labels:
      None
    • Target Version/s:

      Description

      HADOOP-13871 has shown that network problems can kill perf, and that it's v. hard to track down, even if you turn up the logging in hadoop.fs.s3a and com.amazon layers to debug.

      we could maybe improve things by printing out the IPAddress of the s3 endpoint, as that could help with the network tracing. Printing from within hadoop shows the one given to S3a, not a different one returned by any load balancer.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                stevel@apache.org Steve Loughran
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: