This has very little to do with memcached and everything to do with your DNS infrastructure. The client that connects is what does the DNS resolution. memcached has nothing to do with DNS.
FWIW, we avoid dns lookups at all costs for memcached because it is just one more thing that has to happen before I can have my data.
Brian. -------- http://brian.moonspot.net/ On 10/6/09 8:41 PM, Edward M. Goldberg wrote:
I have used Memcached in EC2 now for many deployments and I am seeing issues with DNS names used for Memcache access: 10.1.2.3:11211 vs. memcache.0.my-name.net:11211 I have set the TTL very low to provide for fail over from one server to the next, when new instances are launched. Does anyone have ideas on how I can get the same "Fail Over" I enjoy from DNS? What do you see as the "impact" of DNS look ups on Memcache service? I see /etc/hosts as one solution that keeps the code the same. But updates are hard to distribute... What are your thoughts, solutions? Edward M. Goldberg http://myCloudWatcher.com/
