Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
mongodb-user
Home
+ new post
About this group
Join this group
Message from discussion does primary,secondary order matter in connection string?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Hannes Magnusson  
View profile  
 More options Nov 6 2012, 9:17 pm
From: Hannes Magnusson <han...@10gen.com>
Date: Tue, 6 Nov 2012 18:17:04 -0800
Local: Tues, Nov 6 2012 9:17 pm
Subject: Re: [mongodb-user] does primary,secondary order matter in connection string?
Print | View thread | Show original | Report this message | Find messages by this author
We will always use the first entry in the seed list to discover the
topology of the replicaset, and then match the next server in the
seedlist to our discovery.

The only case where it could possibly matter is if the first node is
down, but the end results would be the same as we will verify the the
entire seed list to our discovered topology.

This should have no affect on the cursor whatsoever.. You are passing
in an array as the second argument to the constructor with
array("replicaSet" => "replicaset-name") right?

-Hannes

On Tue, Nov 6, 2012 at 5:19 PM, Adam Monsen <hair...@gmail.com> wrote:
> Do these two connection strings behave the same?

> 1. mongodb://primary:27017,secondary:27017
> 2. mongodb://secondary:27017,primary:27017

> I was seeing a bunch of "MongoCursorTimeoutException: cursor timed out"
> errors using #2, when I switched to #1 they went away.

> I'm running a 3-node replica set on EC2 instances. Each node runs in a
> different availability zone.

> Each node is MongoDB 2.2.1 on the latest Amazon Linux (2012.09).

> I connect to MongoDB using Doctrine MongoDB, so here are a few other
> moving parts:

> * Symfony v2.0.18
> * doctrine-common b886898821288d305862ee9c567cc5b5cbb4c0dc
> * doctrine-mongodb 727a12d25ba12d18aa293bc6eb61f203a9545912
> * doctrine-mongodb-odm bd65a47c32f9ad9ac888914ab88d89976a5bcfe8
> * 'mongo' from pecl.php.net, version 1.2.12


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google