Uploaded image for project: 'CDH (READ-ONLY)'
  1. CDH (READ-ONLY)
  2. DISTRO-551

Upgrade to CDH 4.5.0 breaks S3 connectivity

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Feedback Received
    • Affects Version/s: CDH4.5.0
    • Fix Version/s: None
    • Component/s: HDFS
    • Labels:
      None
    • Environment:

      Description

      Hi!

      I recently upgraded a cluster to CDH 4.5.0 and noticed that after the upgrade, our pig script that could pull data in from s3 in the past, now just hangs and prints a bunch of these error messages:

      2013-12-15 02:14:09,197 [Finalizer] WARN com.cloudera.org.jets3t.service.impl.rest.httpclient.HttpMethodReleaseInputStream - Attempting to release HttpMethod in finalize() as its response data stream has gone out of scope. This attempt will not always succeed and cannot be relied upon! Please ensure response data streams are always fully consumed or closed to avoid HTTP connection starvation.
      2013-12-15 02:14:09,216 [Finalizer] WARN com.cloudera.org.jets3t.service.impl.rest.httpclient.HttpMethodReleaseInputStream - Attempting to release HttpMethod in finalize() as its response data stream has gone out of scope. This attempt will not always succeed and cannot be relied upon! Please ensure response data streams are always fully consumed or closed to avoid HTTP connection starvation.
      2013-12-15 02:14:09,233 [Finalizer] WARN com.cloudera.org.jets3t.service.impl.rest.httpclient.HttpMethodReleaseInputStream - Attempting to release HttpMethod in finalize() as its response data stream has gone out of scope. This attempt will not always succeed and cannot be relied upon! Please ensure response data streams are always fully consumed or closed to avoid HTTP connection starvation.

      There is a similar problem mentioned here that seems related: http://community.cloudera.com/t5/Storage-Random-Access-HDFS/from-CDH-4-4-0-1-cdh4-4-0-p0-39-to-CDH-4-5-0-1-cdh4-5-0-p0-30/td-p/3869

      I am still using the fs.s3n.awsAccessKeyId and fs.s3n.awsSecretAccessKey in core-site.xml that worked before the upgrade. Interestingly, things worked fine when I was still running pig 0.9.2 against the CDH 4.5.0 cluster, upgrading pig to 0.11 that comes with CDH 4.5.0, however, and things stopped working.

      Any info would be great, thanks!

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              cru steve layland
            • Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: