{"action":"created","issue":{"url":"https://api.github.com/repos/killme2008/xmemcached/issues/37","labels_url":"https://api.github.com/repos/killme2008/xmemcached/issues/37/labels{/name}","comments_url":"https://api.github.com/repos/killme2008/xmemcached/issues/37/comments","events_url":"https://api.github.com/repos/killme2008/xmemcached/issues/37/events","html_url":"https://github.com/killme2008/xmemcached/issues/37","id":113682021,"number":37,"title":"Support for AWS Elasticache Autodiscovery","user":{"login":"marstonstudio","id":1617654,"avatar_url":"https://avatars.githubusercontent.com/u/1617654?v=3","gravatar_id":"","url":"https://api.github.com/users/marstonstudio","html_url":"https://github.com/marstonstudio","followers_url":"https://api.github.com/users/marstonstudio/followers","following_url":"https://api.github.com/users/marstonstudio/following{/other_user}","gists_url":"https://api.github.com/users/marstonstudio/gists{/gist_id}","starred_url":"https://api.github.com/users/marstonstudio/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/marstonstudio/subscriptions","organizations_url":"https://api.github.com/users/marstonstudio/orgs","repos_url":"https://api.github.com/users/marstonstudio/repos","events_url":"https://api.github.com/users/marstonstudio/events{/privacy}","received_events_url":"https://api.github.com/users/marstonstudio/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-10-27T20:28:38Z","updated_at":"2015-11-13T09:35:12Z","closed_at":null,"body":"Request to add support for AWS Autodiscovery to xmemcached\r\nhttp://docs.aws.amazon.com/AmazonElastiCache/latest/UserGuide/AutoDiscovery.html\r\n\r\nAmazon forked the spy client to provide and implementation of this functionality\r\nhttps://github.com/awslabs/aws-elasticache-cluster-client-memcached-for-java/commit/70bf7643963500db20749d97c071b64b954eabb3\r\n\r\nBut we have had recurring problems with Spy client and much prefer xmemcached\r\n\r\nOnly problem with xmemcached is that there is no builtin recovery mechanism if a node is replaced after the client has initialized. A new node will have the same URL but different IP address.\r\n\r\nAny interest?"},"comment":{"url":"https://api.github.com/repos/killme2008/xmemcached/issues/comments/156377416","html_url":"https://github.com/killme2008/xmemcached/issues/37#issuecomment-156377416","issue_url":"https://api.github.com/repos/killme2008/xmemcached/issues/37","id":156377416,"user":{"login":"flozano","id":1159291,"avatar_url":"https://avatars.githubusercontent.com/u/1159291?v=3","gravatar_id":"","url":"https://api.github.com/users/flozano","html_url":"https://github.com/flozano","followers_url":"https://api.github.com/users/flozano/followers","following_url":"https://api.github.com/users/flozano/following{/other_user}","gists_url":"https://api.github.com/users/flozano/gists{/gist_id}","starred_url":"https://api.github.com/users/flozano/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/flozano/subscriptions","organizations_url":"https://api.github.com/users/flozano/orgs","repos_url":"https://api.github.com/users/flozano/repos","events_url":"https://api.github.com/users/flozano/events{/privacy}","received_events_url":"https://api.github.com/users/flozano/received_events","type":"User","site_admin":false},"created_at":"2015-11-13T09:35:12Z","updated_at":"2015-11-13T09:35:12Z","body":"Any update on this topic @killme2008 ? it seems we're seeing more node replacement by AWS these days and it's becoming a problem for us"}}