3 ms·

I'm seeing it as well - majority of connections are being dropped for us atm The Amazon S3 team recently completed some maintenance changes to Amazon S3

by nmjohn 11y ago

I'm seeing it as well - majority of connections are being dropped for us atm The Amazon S3 team recently completed some maintenance changes to Amazon S3’s DNS configuration for the US STANDARD region on July 30th, 2015. You are receiving this email because we noticed that your bucket is still receiving requests on the IP addresses which were removed from DNS rotation. These IP addresses will be disabled on August 10th at 11:00 am PDT, at which time any requests still using those addresses will receive an HTTP 503 response status code. Applications should use the published Amazon S3 DNS names for US STANDARD: either s3.amazonaws.com or s3-external-2.amazonaws.com with their associated time to live (TTL) values. Please refer to our documentation at: http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region for more information on Amazon S3 DNS names. Something to do with that perhaps? AWS sent us that last thursday

cperciva 11y ago
If it is related, someone screwed up badly. I didn't receive such an email; and I'm seeing the same error rate with IPs I resolved 5 minutes ago.
bbrazil 11y ago
Java by default can cache DNS forever, which may be why many people are seeing problems. Set networkaddress.cache.ttl to adjust this. http://javaeesupportpatterns.blogspot.ie/2011/03/java-dns-cache-reference-guide.html http://javaeesupportpatterns.blogspot.ie/2011/03/java-dns-ca... has more detail.
- ork 11y ago
  Reading this article, it seems that starting at 1.6 the default TTL became 30s.
  - Xorlev 11y ago
    It's not true as far as I can tell. You need this flag set or it keeps DNS entries forever, at least on the JVM we run (Oracle, 1.8u51).
    - gnethercutt 11y ago
      The default behavior in Java 7 & 8 is to cache forever when a security manager is installed, and to cache for an implementation-specific period of time when a security manager is not installed. Sans security manager, I see 30s in Java 7 -- reference the DEFAULT_POSITIVE constant in sun.net. InetAddressCachePolicy

by nmjohn 11y ago

cperciva 11y ago

If it is related, someone screwed up badly. I didn't receive such an email; and I'm seeing the same error rate with IPs I resolved 5 minutes ago.

bbrazil 11y ago

Java by default can cache DNS forever, which may be why many people are seeing problems. Set networkaddress.cache.ttl to adjust this. http://javaeesupportpatterns.blogspot.ie/2011/03/java-dns-cache-reference-guide.html http://javaeesupportpatterns.blogspot.ie/2011/03/java-dns-ca... has more detail.

ork 11y ago
Reading this article, it seems that starting at 1.6 the default TTL became 30s.
- Xorlev 11y ago
  It's not true as far as I can tell. You need this flag set or it keeps DNS entries forever, at least on the JVM we run (Oracle, 1.8u51).
  - gnethercutt 11y ago
    The default behavior in Java 7 & 8 is to cache forever when a security manager is installed, and to cache for an implementation-specific period of time when a security manager is not installed. Sans security manager, I see 30s in Java 7 -- reference the DEFAULT_POSITIVE constant in sun.net. InetAddressCachePolicy