Proxy and Availability
Fri, 07/09/2010 - 09:11
Can you shed some light on Availabilty?
Currently, I have my clients talking to the server-side proxy (port 11211) on one membase server. If I add a second server (join cluster), how does this affect availability? If the node with the proxy goes down, how do the clients know about the other node?
Also, how does this change with the upcoming client-side proxy?
thanks.
-Corey
Corey,
With the current implementation, you will want to tell your clients about new servers as they are added. That way, if a server does fail, your client will be able to talk to any remaining ones in the cluster. Since all the servers are running a proxy, you shouldn't have to worry about rehashing issues with adding or removing servers.
Going forward, the upcoming client-side proxy will handle this dynamically. This will be almost identical to how the "smart-clients" for our memcached work (spymemcached or Enyim). Going forward even farther, improvements to client libraries will allow them to not only update automatically but work without a proxy.
A client-side proxy saves you the extra network hop of going to a server-side proxy. A client that doesn't need a proxy at all will improve performance that much more.
Hope that helps, let me know if you have any more questions.
Perry
Forum support is great for free but sometimes you need a guaranteed response time and dedicated resources for your questions or issues.
Consider purchasing enterprise-level support from Membase: http://www.membase.com/products-and-services/overview
Call or email "sales -at- membase -dot- com" today!