Object Creation Hangs If One Node Is Down
We have two servers in a cluster. We have noticed that if one of those servers is down, the creation of the MembaseClient object just hangs forever. This kind of defeats the purpose of a cluster. Is there a way for the framework to see that, ignore that node and pick up on the one that is up and servicing requests instead of continuing to try to make contact with the one that's down?