Support for AWS elasticache auto discovery

[andrewluetgers]

I honestly do not know from the docs if this is actually supported with the correct settings or not. But it would be nice to have. As of now we are just going to run with a single instance because we are in a hurry to get our app out. But we did get bit by this as our session would renew every few mins as it bounced from one server to the other.

The issue is covered in general here http://stackoverflow.com/questions/17046661/how-do-you-implement-aws-elasticache-auto-discovery-for-node-js

[rcoup]

@andrewluetgers You can use the names for each node as shown in the ElastiCache console under "Nodes" for your cluster (eg. api.abcde12345.NNNN.apse2.cache.amazonaws.com where NNNN is 0001,0002,0003,etc) in your node-memcached server array. It won't update if you grow/shrink your cluster, but does prevent the bouncing issue.

Having said that, support for the config get cluster command would be awesomesauce :+1:

[jmreicha]

Any update on this?

[shun-tak]

Support for 'config get cluster' https://github.com/3rd-Eden/memcached/pull/284

[nmaves]

Hard to believe that this was never implemented from end to end.

The config command is nice to have but you still have to create two clients manually and do the interval polling on your own. It would be nice if this library supported it natively.