.NET client won't communicate with cluster successfully configured with hostnames
Running Windows 7 x64 Couchbase 2.0.0
I have a cluster of 2 servers successfully configured to use hostnames. They both show as "up" in the console.
Host 1: host-a.domain.com
Host 2: host-a.domain.com
I have them configured in their respective config sections to use hostnames as well:
<memcached protocol="Binary"> <servers> <add address="host-a.domain.com" port="11211" /> <add address="host-a.domain.com" port="11211" /> </servers> <socketPool connectionTimeout="00:00:02" /> </memcached> --snip-- <servers bucket="lolwut"> <add uri="http://host-a.domain.com:8091/pools" /> <add uri="http://host-b.domain.com:8091/pools" /> </servers>
Then, when I actually call an operation on the CouchbaseClient the operation returns false, unsuccessful.
More intriguingly, if I watch the "ops per second" for the bucket I'm targeting it appears to complete the operation! The result is just never delivered by the .NET client.
Everything works perfectly when Couchbase Server is bound to IP instead of hostname (client configs use hostnames in this case as well).
Upgrading to 2.0.1 (which wipes out the hostname binding btw), did not fix the issue.