Home | Forums | Couchbase | Couchbase Server 1.8.x

app.config configuration settings

3 replies [Last post]
Wed, 05/09/2012 - 11:26
abarney
Offline
Joined: 03/13/2012
Groups: None

In the section of the app.config that defines the URIs in the servers list that is used by the client, is there a recommendation to how many of the servers in the cluster to include? For example, if I have 5 nodes in my cluster with IP addresses 192.168.0.2, 192.168.0.3, 192.168.0.4, 192.168.0.5, and 192.168.0.6.

What is the difference between having this in my app.config

<couchbase>
<servers bucket="default" bucketPassword="">
<add uri="http://192.168.0.2:8091/pools/default"/>
<add uri="http://192.168.0.3:8091/pools/default"/>
<add uri="http://192.168.0.4:8091/pools/default"/>
<add uri="http://192.168.0.5:8091/pools/default"/>
<add uri="http://192.168.0.6:8091/pools/default"/>
</servers>
</couchbase>

versus

<couchbase>
<servers bucket="default" bucketPassword="">
<add uri="http://192.168.0.2:8091/pools/default"/>
<add uri="http://192.168.0.3:8091/pools/default"/>
<add uri="http://192.168.0.4:8091/pools/default"/>
</servers>
</couchbase>

?

Thanks

Top
Mon, 05/21/2012 - 23:50
ingenthr
Offline
Joined: 03/16/2010
Groups:

There is no specific recommendation for number of servers. Three to five is a good number. The client library will try them in sequence until finding one that works correctly.

Top
Thu, 05/31/2012 - 09:02
mayank_connectem
Offline
Joined: 05/31/2012
Groups: None

Hi
i am facing one issue
i have two membase servers and want that if one of them goes down then the other membase will connect automatically
but unable to do so because whenever one of my membase is down my sgsn will try reconnect with the same membase again and again and each time i got the same exception:
Configuration for default bucket was not found.
can any help me out to resolve this issue.

thanks

Top
Tue, 06/05/2012 - 06:26
mayank_connectem
Offline
Joined: 05/31/2012
Groups: None

Hi
i have one point to mention here
i am using couchbase version 1.8 and using three nodes for failover purpose but i am getting some unexpected result in on of the use case:
My server nodes are: 192.168.0.150, 192.168.0.151, 192.168.0.122

now if the first two nodes are down then the client is not able to connect to last node .
and tries again and again to first node i.e 192.168.0.150

Top