Hi Andre,
In the multi-node environments I usually connect each Syracuse server to it's local member of the replication set.  i.e. 3 presentation servers with a local copy of Mongo as a member of the replica set.  Syracuse on presentation1 connects to Mongo on presentation1, Syracuse on presentation2 connects to Mongo on presentation2, etc

If you only have one instance of Syracuse then I would connect it to the primary host of the replica set (the one with priority set to 1).  Make sure the "host" is set correctly when you run cfg = rs.conf() in MongoDB. 

Hi Andre,
In the multi-node environments I usually connect each Syracuse server to it's local member of the replication set.  i.e. 3 presentation servers with a local copy of Mongo as a member of the replica set.  Syracuse on presentation1 connects to Mongo on presentation1, Syracuse on presentation2 connects to Mongo on presentation2, etc

If you only have one instance of Syracuse then I would connect it to the primary host of the replica set (the one with priority set to 1).  Make sure the "host" is set correctly when you run cfg = rs.conf() in MongoDB. 

Hi Carl, 

This was an issue 4 years ago :-) that now is solved. We usually deploy syracuse clusters connected to mongo cluster for high availability solutions, also with multiple apache hosts on previous versions. I think that the connection configuration file was not adequately created at that time. Regards.