Specifying ReplicateTo.One in ExecuteStore times out

I have a test cluster using 5 desktop machines running 2.2 enterprise, I have the replication factor set to 1 for the default bucket.

I can do normal stores and everything appears fine, but when I try to set the durability of ExecuteStore to ReplicateTo.One, I get a timeout error after 60 seconds

This is the call I'm making:
var result = _client.ExecuteStore(StoreMode.Set, key, data, PersistTo.Zero, ReplicateTo.One)

And the log results that show the observe not finding the key in the replica

18:56:00.573 Acquiring stream from pool. 10.151.4.129:11210
18:56:00.573 Socket 03a42f7d-0802-4915-8cad-e3f3bb3e1457 was reset
18:56:00.573 Socket was reset. 03a42f7d-0802-4915-8cad-e3f3bb3e1457
18:56:00.573 Releasing socket 03a42f7d-0802-4915-8cad-e3f3bb3e1457
18:56:00.573 Are we alive? True
18:56:00.573 Node: 10.151.4.129:11210, Result: FoundPersisted, Master: True, Cas: 3973923562848, Key: 2013-01-01_f88e8ac2a42e4d91a5da000b429f5ca2
18:56:00.573 Acquiring stream from pool. 10.151.4.116:11210
18:56:00.573 Socket 540b785d-e334-46e4-a362-e9aea56e84fa was reset
18:56:00.573 Socket was reset. 540b785d-e334-46e4-a362-e9aea56e84fa
18:56:00.573 Releasing socket 540b785d-e334-46e4-a362-e9aea56e84fa
18:56:00.573 Are we alive? True
18:56:00.573 Node: 10.151.4.116:11210, Result: NotFound, Master: False, Cas: 0, Key: 2013-01-01_f88e8ac2a42e4d91a5da000b429f5ca2
18:56:00.573 Master Persisted: True, Replica Found: 0, Replica Persisted: 0
18:56:00.573 Expected Replication: False, Expected Persistence: True, Expected Master Persistence: True
18:56:01.073 Acquiring stream from pool. 10.151.4.129:11210
18:56:01.073 Socket 03a42f7d-0802-4915-8cad-e3f3bb3e1457 was reset
18:56:01.073 Socket was reset. 03a42f7d-0802-4915-8cad-e3f3bb3e1457
18:56:01.073 Releasing socket 03a42f7d-0802-4915-8cad-e3f3bb3e1457
18:56:01.073 Are we alive? True
18:56:01.073 Node: 10.151.4.129:11210, Result: FoundPersisted, Master: True, Cas: 3973923562848, Key: 2013-01-01_f88e8ac2a42e4d91a5da000b429f5ca2
18:56:01.073 Acquiring stream from pool. 10.151.4.116:11210
18:56:01.073 Socket 540b785d-e334-46e4-a362-e9aea56e84fa was reset
18:56:01.073 Socket was reset. 540b785d-e334-46e4-a362-e9aea56e84fa
18:56:01.073 Releasing socket 540b785d-e334-46e4-a362-e9aea56e84fa
18:56:01.073 Are we alive? True
18:56:01.073 Node: 10.151.4.116:11210, Result: NotFound, Master: False, Cas: 0, Key: 2013-01-01_f88e8ac2a42e4d91a5da000b429f5ca2
18:56:01.073 Master Persisted: True, Replica Found: 0, Replica Persisted: 0
18:56:01.073 Expected Replication: False, Expected Persistence: True, Expected Master Persistence: True

I'm not sure what I can look into to find out why the replication is not working as expected, are there any special configuration options or settings required?

I just realized that replication is not functioning at all, there appears to be no info in the log with any errors, but the Server Nodes pane it says Items (Active / Replica) = 68.1K / 0 for all of the nodes.

It looks the same as this unresolved bug report: http://www.couchbase.com/issues/browse/MB-7977

What happen when you insert documents from the console? (do you see replicas in the nodes?)
It looks to me that you may have a network issue.

The same appears to happen when I created a few documents using the web interface, all of the replica counts say 0

The windows firewall is turned on(I dont have permissions to completly turn it off on these machines) but I opened the following ports and everything else appears to be working
4369, 8091, 8092, 11211, 11210, 21100-21199

1 Answer

« Back to question.

Turns out I just didn't have enough ports open, I used process explorer to see what ports each process was listening on, and after specifying the following ports to be open in my firewall config replication started working as expected:

4369, 8091, 8092, 11209-11213, 21100-21199