Enyim Membase client receives POOLFail periodically
We've managed to get a cluster of Membase cache servers up and running on Amazon EC2 and managed to get the Enyim Membase to connect to them successfully. But weirdly we get these error messages periodically when the the pool url points to a Load Balancer:
2010-07-28 13:44:22,340  WARN Membase.Store.MessageStreamListener [(null)] - Current pool [url]http://xxx:8080/pools/default/bucketsStreaming/default[/url] has failed.
2010-07-28 13:44:22,340  WARN Membase.Store.MessageStreamListener [(null)] - All pools are dead, sleeping a while.
2010-07-28 13:45:28,920  ERROR Membase.Store.MessageStreamListener [(null)] - POOLFAIL
System.IO.IOException: Unable to read data from the transport connection: The connection was closed.
at System.Net.ConnectStream.Read(Byte buffer, Int32 offset, Int32 size)
at Membase.Store.MessageStreamListener.MessageReader.Start(Uri uri)
at Membase.Store.MessageStreamListener.Work(Object state)
This goes away when I replace the Load Balancer url with one of the nodes in the cluster, but I'm just curious as to why this can be a problem when the url points to a load balancer.