|| at Jul 23, 2012 at 6:19 pm
I believe the behavior that you want can be accomplished by creating a
custom "NodeFailurePolicy" that never "fails" a node. If for some reason a
node can't be reached, calls to it will just fail until it comes back
online. As far as I can tell (from testing and reading the source) keys
will not be remapped.
*config.SocketPool.FailurePolicyFactory = new NeverFailPolicyFactory();*
public class NeverFailPolicyFactory : INodeFailurePolicyFactory
public INodeFailurePolicy Create(IMemcachedNode node)
public class NeverFailPolicy : INodeFailurePolicy
public static NeverFailPolicy Instance = new NeverFailPolicy();
public bool ShouldFail()
On Wednesday, June 27, 2012 6:54:32 AM UTC-7, NCSUWolf99 wrote:
I'd rather have the operation treated as a miss or failure rather than
having the key(s) get mapped to a different server in the pool.