demitri.barout...@gmail.com> wrote:
> We're currently running all our MongoDB instances with version 2.0.5 of
> the MongoDB server with replica-sets.
> Each server is hosted on a separate machine to cater for fail-over.

> We are using version 1.3.0.4309 of the C# Driver and we're seeing the
> following error. It happens just after a network failure where one of the
> server instances takes over as primary in the replica-set:

> Safemode detected an error 'not master'. (Response was { "err" : "not
> master", "code" : 10058, "n" : 0, "lastOp" : NumberLong(0), "connectionId"
> : 140567, "ok" : 1.0 }).

> Here's the stack-trace of that error occurrence:
>    at
> MongoDB.Driver.Internal.MongoConnection.SendMessage(MongoRequestMessage
> message, SafeMode safeMode)
>    at MongoDB.Driver.MongoCollection.InsertBatch(Type nominalType,
> IEnumerable documents, MongoInsertOptions options)
>    at MongoDB.Driver.MongoCollection.Insert(Type nominalType, Object
> document, MongoInsertOptions options)
>    at MongoDB.Driver.MongoCollection.Insert(Type nominalType, Object
> document, SafeMode safeMode)
>    at MongoDB.Driver.MongoCollection.Insert(Type nominalType, Object
> document)
>    at MongoDB.Driver.MongoCollection.Insert[TNominalType](TNominalType
> document)

> Our connection string has all three server names and ports as per the
> documentation.

> It appears as if the MongoDB Connection in the C# driver is not checking
> that the one it knows to be primary is still the primary when doing a write
> operation. The only way we can recover from this is to restart the
> application pool the web application is running in, thereby forcing the
> next request to re-create the database connection object and then it knows
> which of the three server instance is now the primary again.

> Is this perhaps a known issue with the version of the server software and
> C# driver we are using? We are planning on updating the code-base to use
> the latest version of the C# driver shortly.

> Thanks in advance

> Regards,
> Demitri

}

On Tuesday, 3 July 2012 13:15:44 UTC+2, Scott Hernandez wrote:

> How are you connecting to the server? What connection string (URI) or
> constructor (MongoServerSettings) are you using?

> On Tue, Jul 3, 2012 at 11:36 AM, Demitri Baroutsos <
> demitri.barout...@gmail.com> wrote:

>> We're currently running all our MongoDB instances with version 2.0.5 of
>> the MongoDB server with replica-sets.
>> Each server is hosted on a separate machine to cater for fail-over.

>> We are using version 1.3.0.4309 of the C# Driver and we're seeing the
>> following error. It happens just after a network failure where one of the
>> server instances takes over as primary in the replica-set:

>> Safemode detected an error 'not master'. (Response was { "err" : "not
>> master", "code" : 10058, "n" : 0, "lastOp" : NumberLong(0), "connectionId"
>> : 140567, "ok" : 1.0 }).

>> Here's the stack-trace of that error occurrence:
>>    at
>> MongoDB.Driver.Internal.MongoConnection.SendMessage(MongoRequestMessage
>> message, SafeMode safeMode)
>>    at MongoDB.Driver.MongoCollection.InsertBatch(Type nominalType,
>> IEnumerable documents, MongoInsertOptions options)
>>    at MongoDB.Driver.MongoCollection.Insert(Type nominalType, Object
>> document, MongoInsertOptions options)
>>    at MongoDB.Driver.MongoCollection.Insert(Type nominalType, Object
>> document, SafeMode safeMode)
>>    at MongoDB.Driver.MongoCollection.Insert(Type nominalType, Object
>> document)
>>    at MongoDB.Driver.MongoCollection.Insert[TNominalType](TNominalType
>> document)

>> Our connection string has all three server names and ports as per the
>> documentation.

>> It appears as if the MongoDB Connection in the C# driver is not checking
>> that the one it knows to be primary is still the primary when doing a write
>> operation. The only way we can recover from this is to restart the
>> application pool the web application is running in, thereby forcing the
>> next request to re-create the database connection object and then it knows
>> which of the three server instance is now the primary again.

>> Is this perhaps a known issue with the version of the server software and
>> C# driver we are using? We are planning on updating the code-base to use
>> the latest version of the C# driver shortly.

>> Thanks in advance

>> Regards,
>> Demitri

On Tuesday, July 3, 2012 7:01:34 AM UTC-5, Demitri Baroutsos wrote:

> Our connection string format is as follows:

> mongodb://mongoDBUser:MongoDBPassw...@10.40.123.4:27017,10.80.123.5:27017,
> 10.80.123.6:27017/?safe=true;w=2;wtimeoutMS=2000;slaveOk=true

> We keep a static instance of the server and database objects as follows:

>         private static MongoServer _server;
>         private static MongoServer DBServer
>         {
>             get
>             {
>                 if (_server == null)
>                 {
>                     _server =
> MongoServer.Create(ConfigurationManager.ConnectionStrings["MyMongoConnectio nString"].ToString());
>                 }
>                 return _server;
>             }
>         }

>         private static MongoDatabase _db;
>         internal static MongoDatabase DB
>         {
>             get
>             {
>                 if (_db == null)
>                 {
>                     _db = DBServer.GetDatabase("MyMongoDBName");
>                 }
>                 return _db;
>             }
>         }

> We fetch collections using the DB object as follows using generic types:

> internal static MongoCollection GetCollection<T>()
> {
>     return DB.GetCollection(typeof(T), typeof(T).Name);
> }

> Could it be that the issue is caused by us keeping static instances of the
> DB and Server objects in a web environment?

> Just to re-iterate the issue around server instance connectivity. The web
> server maintains connection with the current primary DB server. However the
> two other instances (according to their logs) lose connectivity to the
> current primary and one of them is elected as primary. Now when the web
> server tries to write to the original primary it appears that it is still
> seeing this instance as the primary instance and thus returns the Safemode
> detected an error 'not master'. error when in fact, one of the other
> servers has taken over as primary. Only when either re-starting the
> app-pool on the web server or restarting the MongoDB instance that WAS the
> primary resolves the exception error.

> Regards,
> Demitri

> On Tuesday, 3 July 2012 13:15:44 UTC+2, Scott Hernandez wrote:

>> How are you connecting to the server? What connection string (URI) or
>> constructor (MongoServerSettings) are you using?

>> On Tue, Jul 3, 2012 at 11:36 AM, Demitri Baroutsos <
>> demitri.barout...@gmail.com> wrote:

>>> We're currently running all our MongoDB instances with version 2.0.5 of
>>> the MongoDB server with replica-sets.
>>> Each server is hosted on a separate machine to cater for fail-over.

>>> We are using version 1.3.0.4309 of the C# Driver and we're seeing the
>>> following error. It happens just after a network failure where one of the
>>> server instances takes over as primary in the replica-set:

>>> Safemode detected an error 'not master'. (Response was { "err" : "not
>>> master", "code" : 10058, "n" : 0, "lastOp" : NumberLong(0), "connectionId"
>>> : 140567, "ok" : 1.0 }).

>>> Here's the stack-trace of that error occurrence:
>>>    at
>>> MongoDB.Driver.Internal.MongoConnection.SendMessage(MongoRequestMessage
>>> message, SafeMode safeMode)
>>>    at MongoDB.Driver.MongoCollection.InsertBatch(Type nominalType,
>>> IEnumerable documents, MongoInsertOptions options)
>>>    at MongoDB.Driver.MongoCollection.Insert(Type nominalType, Object
>>> document, MongoInsertOptions options)
>>>    at MongoDB.Driver.MongoCollection.Insert(Type nominalType, Object
>>> document, SafeMode safeMode)
>>>    at MongoDB.Driver.MongoCollection.Insert(Type nominalType, Object
>>> document)
>>>    at MongoDB.Driver.MongoCollection.Insert[TNominalType](TNominalType
>>> document)

>>> Our connection string has all three server names and ports as per the
>>> documentation.

>>> It appears as if the MongoDB Connection in the C# driver is not checking
>>> that the one it knows to be primary is still the primary when doing a write
>>> operation. The only way we can recover from this is to restart the
>>> application pool the web application is running in, thereby forcing the
>>> next request to re-create the database connection object and then it knows
>>> which of the three server instance is now the primary again.

>>> Is this perhaps a known issue with the version of the server software
>>> and C# driver we are using? We are planning on updating the code-base to
>>> use the latest version of the C# driver shortly.

>>> Thanks in advance

>>> Regards,
>>> Demitri

On Tue, Jul 3, 2012 at 8:21 AM, craiggwilson <craiggwil...@gmail.com> wrote:
> I'm not sure if it is known issue or not with that  version, but I do know
> a lot of work has gone into replica set connections since the release of
> that version, which was a long time ago.  If you are planning on updating,
> then that should fix the issue.

> On Tuesday, July 3, 2012 7:01:34 AM UTC-5, Demitri Baroutsos wrote:

>> Our connection string format is as follows:

>> mongodb://mongoDBUser:**MongoDBPassw...@10.40.123.4:**27017<http://mongoDBUser:MongoDBPassw...@10.40.123.4:27017>
>> ,10.80.123.5:27017,10.80.**123.6:27017/?safe=true;w=2;**
>> wtimeoutMS=2000;slaveOk=true<http://10.80.123.6:27017/?safe=true;w=2;wtimeoutMS=2000;slaveOk=true>

>> We keep a static instance of the server and database objects as follows:

>>         private static MongoServer _server;
>>         private static MongoServer DBServer
>>         {
>>             get
>>             {
>>                 if (_server == null)
>>                 {
>>                     _server = MongoServer.Create(**ConfigurationManager.*
>> *ConnectionStrings["**MyMongoConnectionString"].**ToString());
>>                 }
>>                 return _server;
>>             }
>>         }

>>         private static MongoDatabase _db;
>>         internal static MongoDatabase DB
>>         {
>>             get
>>             {
>>                 if (_db == null)
>>                 {
>>                     _db = DBServer.GetDatabase("**MyMongoDBName");
>>                 }
>>                 return _db;
>>             }
>>         }

>> We fetch collections using the DB object as follows using generic types:

>> internal static MongoCollection GetCollection<T>()
>> {
>>     return DB.GetCollection(typeof(T), typeof(T).Name);
>> }

>> Could it be that the issue is caused by us keeping static instances of
>> the DB and Server objects in a web environment?

>> Just to re-iterate the issue around server instance connectivity. The web
>> server maintains connection with the current primary DB server. However the
>> two other instances (according to their logs) lose connectivity to the
>> current primary and one of them is elected as primary. Now when the web
>> server tries to write to the original primary it appears that it is still
>> seeing this instance as the primary instance and thus returns the Safemode
>> detected an error 'not master'. error when in fact, one of the other
>> servers has taken over as primary. Only when either re-starting the
>> app-pool on the web server or restarting the MongoDB instance that WAS the
>> primary resolves the exception error.

>> Regards,
>> Demitri

>> On Tuesday, 3 July 2012 13:15:44 UTC+2, Scott Hernandez wrote:

>>> How are you connecting to the server? What connection string (URI) or
>>> constructor (MongoServerSettings) are you using?

>>> On Tue, Jul 3, 2012 at 11:36 AM, Demitri Baroutsos <
>>> demitri.barout...@gmail.com> wrote:

>>>> We're currently running all our MongoDB instances with version 2.0.5 of
>>>> the MongoDB server with replica-sets.
>>>> Each server is hosted on a separate machine to cater for fail-over.

>>>> We are using version 1.3.0.4309 of the C# Driver and we're seeing the
>>>> following error. It happens just after a network failure where one of the
>>>> server instances takes over as primary in the replica-set:

>>>> Safemode detected an error 'not master'. (Response was { "err" : "not
>>>> master", "code" : 10058, "n" : 0, "lastOp" : NumberLong(0), "connectionId"
>>>> : 140567, "ok" : 1.0 }).

>>>> Here's the stack-trace of that error occurrence:
>>>>    at MongoDB.Driver.Internal.**MongoConnection.SendMessage(**MongoRequestMessage
>>>> message, SafeMode safeMode)
>>>>    at MongoDB.Driver.**MongoCollection.InsertBatch(**Type nominalType,
>>>> IEnumerable documents, MongoInsertOptions options)
>>>>    at MongoDB.Driver.**MongoCollection.Insert(Type nominalType, Object
>>>> document, MongoInsertOptions options)
>>>>    at MongoDB.Driver.**MongoCollection.Insert(Type nominalType, Object
>>>> document, SafeMode safeMode)
>>>>    at MongoDB.Driver.**MongoCollection.Insert(Type nominalType, Object
>>>> document)
>>>>    at MongoDB.Driver.**MongoCollection.Insert[**TNominalType](TNominalType
>>>> document)

>>>> Our connection string has all three server names and ports as per the
>>>> documentation.

>>>> It appears as if the MongoDB Connection in the C# driver is not
>>>> checking that the one it knows to be primary is still the primary when
>>>> doing a write operation. The only way we can recover from this is to
>>>> restart the application pool the web application is running in, thereby
>>>> forcing the next request to re-create the database connection object and
>>>> then it knows which of the three server instance is now the primary again.

>>>> Is this perhaps a known issue with the version of the server software
>>>> and C# driver we are using? We are planning on updating the code-base to
>>>> use the latest version of the C# driver shortly.

>>>> Thanks in advance

>>>> Regards,
>>>> Demitri

On Tuesday, 3 July 2012 12:36:58 UTC+2, Demitri Baroutsos wrote:

> We're currently running all our MongoDB instances with version 2.0.5 of
> the MongoDB server with replica-sets.
> Each server is hosted on a separate machine to cater for fail-over.

> We are using version 1.3.0.4309 of the C# Driver and we're seeing the
> following error. It happens just after a network failure where one of the
> server instances takes over as primary in the replica-set:

> Safemode detected an error 'not master'. (Response was { "err" : "not
> master", "code" : 10058, "n" : 0, "lastOp" : NumberLong(0), "connectionId"
> : 140567, "ok" : 1.0 }).

> Here's the stack-trace of that error occurrence:
>    at
> MongoDB.Driver.Internal.MongoConnection.SendMessage(MongoRequestMessage
> message, SafeMode safeMode)
>    at MongoDB.Driver.MongoCollection.InsertBatch(Type nominalType,
> IEnumerable documents, MongoInsertOptions options)
>    at MongoDB.Driver.MongoCollection.Insert(Type nominalType, Object
> document, MongoInsertOptions options)
>    at MongoDB.Driver.MongoCollection.Insert(Type nominalType, Object
> document, SafeMode safeMode)
>    at MongoDB.Driver.MongoCollection.Insert(Type nominalType, Object
> document)
>    at MongoDB.Driver.MongoCollection.Insert[TNominalType](TNominalType
> document)

> Our connection string has all three server names and ports as per the
> documentation.

> It appears as if the MongoDB Connection in the C# driver is not checking
> that the one it knows to be primary is still the primary when doing a write
> operation. The only way we can recover from this is to restart the
> application pool the web application is running in, thereby forcing the
> next request to re-create the database connection object and then it knows
> which of the three server instance is now the primary again.

> Is this perhaps a known issue with the version of the server software and
> C# driver we are using? We are planning on updating the code-base to use
> the latest version of the C# driver shortly.

> Thanks in advance

> Regards,
> Demitri

demitri.barout...@gmail.com> wrote:
> Thanks for the reply Robert.

> We do cater for exceptions and don't expect the driver to do all the work
> for us. However every subsequent request to the database fails when
> attempting to write until we restart the app pool/IIS or the MongoDB
> instance that used to be primary for that replica-set.

> Regards,
> Demitri

> On Tuesday, 3 July 2012 12:36:58 UTC+2, Demitri Baroutsos wrote:

>> We're currently running all our MongoDB instances with version 2.0.5 of
>> the MongoDB server with replica-sets.
>> Each server is hosted on a separate machine to cater for fail-over.

>> We are using version 1.3.0.4309 of the C# Driver and we're seeing the
>> following error. It happens just after a network failure where one of the
>> server instances takes over as primary in the replica-set:

>> Safemode detected an error 'not master'. (Response was { "err" : "not
>> master", "code" : 10058, "n" : 0, "lastOp" : NumberLong(0), "connectionId"
>> : 140567, "ok" : 1.0 }).

>> Here's the stack-trace of that error occurrence:
>>    at MongoDB.Driver.Internal.**MongoConnection.SendMessage(**MongoRequestMessage
>> message, SafeMode safeMode)
>>    at MongoDB.Driver.**MongoCollection.InsertBatch(**Type nominalType,
>> IEnumerable documents, MongoInsertOptions options)
>>    at MongoDB.Driver.**MongoCollection.Insert(Type nominalType, Object
>> document, MongoInsertOptions options)
>>    at MongoDB.Driver.**MongoCollection.Insert(Type nominalType, Object
>> document, SafeMode safeMode)
>>    at MongoDB.Driver.**MongoCollection.Insert(Type nominalType, Object
>> document)
>>    at MongoDB.Driver.**MongoCollection.Insert[**TNominalType](TNominalType
>> document)

>> Our connection string has all three server names and ports as per the
>> documentation.

>> It appears as if the MongoDB Connection in the C# driver is not checking
>> that the one it knows to be primary is still the primary when doing a write
>> operation. The only way we can recover from this is to restart the
>> application pool the web application is running in, thereby forcing the
>> next request to re-create the database connection object and then it knows
>> which of the three server instance is now the primary again.

>> Is this perhaps a known issue with the version of the server software and
>> C# driver we are using? We are planning on updating the code-base to use
>> the latest version of the C# driver shortly.

>> Thanks in advance

>> Regards,
>> Demitri

On Tuesday, 3 July 2012 18:21:07 UTC+2, Robert Stam wrote:

> Can you try with a current version of the C# driver? Either 1.4.2 or 1.5.

> I can't find any existing JIRA ticket that would be similar to what you
> are describing.

> On Tue, Jul 3, 2012 at 12:04 PM, Demitri Baroutsos <
> demitri.barout...@gmail.com> wrote:

>> Thanks for the reply Robert.

>> We do cater for exceptions and don't expect the driver to do all the work
>> for us. However every subsequent request to the database fails when
>> attempting to write until we restart the app pool/IIS or the MongoDB
>> instance that used to be primary for that replica-set.

>> Regards,
>> Demitri

>> On Tuesday, 3 July 2012 12:36:58 UTC+2, Demitri Baroutsos wrote:

>>> We're currently running all our MongoDB instances with version 2.0.5 of
>>> the MongoDB server with replica-sets.
>>> Each server is hosted on a separate machine to cater for fail-over.

>>> We are using version 1.3.0.4309 of the C# Driver and we're seeing the
>>> following error. It happens just after a network failure where one of the
>>> server instances takes over as primary in the replica-set:

>>> Safemode detected an error 'not master'. (Response was { "err" : "not
>>> master", "code" : 10058, "n" : 0, "lastOp" : NumberLong(0), "connectionId"
>>> : 140567, "ok" : 1.0 }).

>>> Here's the stack-trace of that error occurrence:
>>>    at MongoDB.Driver.Internal.**MongoConnection.SendMessage(**MongoRequestMessage
>>> message, SafeMode safeMode)
>>>    at MongoDB.Driver.**MongoCollection.InsertBatch(**Type nominalType,
>>> IEnumerable documents, MongoInsertOptions options)
>>>    at MongoDB.Driver.**MongoCollection.Insert(Type nominalType, Object
>>> document, MongoInsertOptions options)
>>>    at MongoDB.Driver.**MongoCollection.Insert(Type nominalType, Object
>>> document, SafeMode safeMode)
>>>    at MongoDB.Driver.**MongoCollection.Insert(Type nominalType, Object
>>> document)
>>>    at MongoDB.Driver.**MongoCollection.Insert[**TNominalType](TNominalType
>>> document)

>>> Our connection string has all three server names and ports as per the
>>> documentation.

>>> It appears as if the MongoDB Connection in the C# driver is not checking
>>> that the one it knows to be primary is still the primary when doing a write
>>> operation. The only way we can recover from this is to restart the
>>> application pool the web application is running in, thereby forcing the
>>> next request to re-create the database connection object and then it knows
>>> which of the three server instance is now the primary again.

>>> Is this perhaps a known issue with the version of the server software
>>> and C# driver we are using? We are planning on updating the code-base to
>>> use the latest version of the C# driver shortly.

>>> Thanks in advance

>>> Regards,
>>> Demitri

On Wednesday, 4 July 2012 09:18:10 UTC+2, Demitri Baroutsos wrote:

> Thanks Robert - we will try with the latest driver and see if the problem
> persists.

> Regards,
> Demitri

> On Tuesday, 3 July 2012 18:21:07 UTC+2, Robert Stam wrote:

>> Can you try with a current version of the C# driver? Either 1.4.2 or 1.5.

>> I can't find any existing JIRA ticket that would be similar to what you
>> are describing.

>> On Tue, Jul 3, 2012 at 12:04 PM, Demitri Baroutsos <
>> demitri.barout...@gmail.com> wrote:

>>> Thanks for the reply Robert.

>>> We do cater for exceptions and don't expect the driver to do all the
>>> work for us. However every subsequent request to the database fails when
>>> attempting to write until we restart the app pool/IIS or the MongoDB
>>> instance that used to be primary for that replica-set.

>>> Regards,
>>> Demitri

>>> On Tuesday, 3 July 2012 12:36:58 UTC+2, Demitri Baroutsos wrote:

>>>> We're currently running all our MongoDB instances with version 2.0.5 of
>>>> the MongoDB server with replica-sets.
>>>> Each server is hosted on a separate machine to cater for fail-over.

>>>> We are using version 1.3.0.4309 of the C# Driver and we're seeing the
>>>> following error. It happens just after a network failure where one of the
>>>> server instances takes over as primary in the replica-set:

>>>> Safemode detected an error 'not master'. (Response was { "err" : "not
>>>> master", "code" : 10058, "n" : 0, "lastOp" : NumberLong(0), "connectionId"
>>>> : 140567, "ok" : 1.0 }).

>>>> Here's the stack-trace of that error occurrence:
>>>>    at MongoDB.Driver.Internal.**MongoConnection.SendMessage(**MongoRequestMessage
>>>> message, SafeMode safeMode)
>>>>    at MongoDB.Driver.**MongoCollection.InsertBatch(**Type nominalType,
>>>> IEnumerable documents, MongoInsertOptions options)
>>>>    at MongoDB.Driver.**MongoCollection.Insert(Type nominalType, Object
>>>> document, MongoInsertOptions options)
>>>>    at MongoDB.Driver.**MongoCollection.Insert(Type nominalType, Object
>>>> document, SafeMode safeMode)
>>>>    at MongoDB.Driver.**MongoCollection.Insert(Type nominalType, Object
>>>> document)
>>>>    at MongoDB.Driver.**MongoCollection.Insert[**TNominalType](TNominalType
>>>> document)

>>>> Our connection string has all three server names and ports as per the
>>>> documentation.

>>>> It appears as if the MongoDB Connection in the C# driver is not
>>>> checking that the one it knows to be primary is still the primary when
>>>> doing a write operation. The only way we can recover from this is to
>>>> restart the application pool the web application is running in, thereby
>>>> forcing the next request to re-create the database connection object and
>>>> then it knows which of the three server instance is now the primary again.

>>>> Is this perhaps a known issue with the version of the server software
>>>> and C# driver we are using? We are planning on updating the code-base to
>>>> use the latest version of the C# driver shortly.

>>>> Thanks in advance

>>>> Regards,
>>>> Demitri

demitri.barout...@gmail.com> wrote:
> Just an update - we needed a fix quite urgently so we deployed latest
> build of our code (removed use of static instances of Database and Server
> contexts, we create instances on-demand now) using the latest C# driver as
> well.

> So far we've not encountered any issues with fail-over causing problems.

> Regards,
> Demitri

> On Wednesday, 4 July 2012 09:18:10 UTC+2, Demitri Baroutsos wrote:

>> Thanks Robert - we will try with the latest driver and see if the problem
>> persists.

>> Regards,
>> Demitri

>> On Tuesday, 3 July 2012 18:21:07 UTC+2, Robert Stam wrote:

>>> Can you try with a current version of the C# driver? Either 1.4.2 or 1.5.

>>> I can't find any existing JIRA ticket that would be similar to what you
>>> are describing.

>>> On Tue, Jul 3, 2012 at 12:04 PM, Demitri Baroutsos <
>>> demitri.barout...@gmail.com> wrote:

>>>> Thanks for the reply Robert.

>>>> We do cater for exceptions and don't expect the driver to do all the
>>>> work for us. However every subsequent request to the database fails when
>>>> attempting to write until we restart the app pool/IIS or the MongoDB
>>>> instance that used to be primary for that replica-set.

>>>> Regards,
>>>> Demitri

>>>> On Tuesday, 3 July 2012 12:36:58 UTC+2, Demitri Baroutsos wrote:

>>>>> We're currently running all our MongoDB instances with version 2.0.5
>>>>> of the MongoDB server with replica-sets.
>>>>> Each server is hosted on a separate machine to cater for fail-over.

>>>>> We are using version 1.3.0.4309 of the C# Driver and we're seeing the
>>>>> following error. It happens just after a network failure where one of the
>>>>> server instances takes over as primary in the replica-set:

>>>>> Safemode detected an error 'not master'. (Response was { "err" : "not
>>>>> master", "code" : 10058, "n" : 0, "lastOp" : NumberLong(0), "connectionId"
>>>>> : 140567, "ok" : 1.0 }).

>>>>> Here's the stack-trace of that error occurrence:
>>>>>    at MongoDB.Driver.Internal.**MongoC**onnection.SendMessage(**
>>>>> MongoReq**uestMessage message, SafeMode safeMode)
>>>>>    at MongoDB.Driver.**MongoCollection**.InsertBatch(**Type
>>>>> nominalType, IEnumerable documents, MongoInsertOptions options)
>>>>>    at MongoDB.Driver.**MongoCollection**.Insert(Type nominalType,
>>>>> Object document, MongoInsertOptions options)
>>>>>    at MongoDB.Driver.**MongoCollection**.Insert(Type nominalType,
>>>>> Object document, SafeMode safeMode)
>>>>>    at MongoDB.Driver.**MongoCollection**.Insert(Type nominalType,
>>>>> Object document)
>>>>>    at MongoDB.Driver.**MongoCollection**.Insert[**TNominalType](**TNominalType
>>>>> document)

>>>>> Our connection string has all three server names and ports as per the
>>>>> documentation.

>>>>> It appears as if the MongoDB Connection in the C# driver is not
>>>>> checking that the one it knows to be primary is still the primary when
>>>>> doing a write operation. The only way we can recover from this is to
>>>>> restart the application pool the web application is running in, thereby
>>>>> forcing the next request to re-create the database connection object and
>>>>> then it knows which of the three server instance is now the primary again.

>>>>> Is this perhaps a known issue with the version of the server software
>>>>> and C# driver we are using? We are planning on updating the code-base to
>>>>> use the latest version of the C# driver shortly.

>>>>> Thanks in advance

>>>>> Regards,
>>>>> Demitri

> Thanks for the update.

> MongoServer.Create always returns the same instance of MongoServer when
> called with the same parameters, so even though you may be calling
> MongoServer.Create on demand, you're still reusing the single instance of
> MongoServer.

> On Tue, Jul 10, 2012 at 4:31 AM, Demitri Baroutsos <
> demitri.barout...@gmail.com> wrote:

>> Just an update - we needed a fix quite urgently so we deployed latest
>> build of our code (removed use of static instances of Database and Server
>> contexts, we create instances on-demand now) using the latest C# driver as
>> well.

>> So far we've not encountered any issues with fail-over causing problems.

>> Regards,
>> Demitri

>> On Wednesday, 4 July 2012 09:18:10 UTC+2, Demitri Baroutsos wrote:

>>> Thanks Robert - we will try with the latest driver and see if the
>>> problem persists.

>>> Regards,
>>> Demitri

>>> On Tuesday, 3 July 2012 18:21:07 UTC+2, Robert Stam wrote:

>>>> Can you try with a current version of the C# driver? Either 1.4.2 or
>>>> 1.5.

>>>> I can't find any existing JIRA ticket that would be similar to what you
>>>> are describing.

>>>> On Tue, Jul 3, 2012 at 12:04 PM, Demitri Baroutsos <
>>>> demitri.barout...@gmail.com> wrote:

>>>>> Thanks for the reply Robert.

>>>>> We do cater for exceptions and don't expect the driver to do all the
>>>>> work for us. However every subsequent request to the database fails when
>>>>> attempting to write until we restart the app pool/IIS or the MongoDB
>>>>> instance that used to be primary for that replica-set.

>>>>> Regards,
>>>>> Demitri

>>>>> On Tuesday, 3 July 2012 12:36:58 UTC+2, Demitri Baroutsos wrote:

>>>>>> We're currently running all our MongoDB instances with version 2.0.5
>>>>>> of the MongoDB server with replica-sets.
>>>>>> Each server is hosted on a separate machine to cater for fail-over.

>>>>>> We are using version 1.3.0.4309 of the C# Driver and we're seeing the
>>>>>> following error. It happens just after a network failure where one of the
>>>>>> server instances takes over as primary in the replica-set:

>>>>>> Safemode detected an error 'not master'. (Response was { "err" : "not
>>>>>> master", "code" : 10058, "n" : 0, "lastOp" : NumberLong(0), "connectionId"
>>>>>> : 140567, "ok" : 1.0 }).

>>>>>> Here's the stack-trace of that error occurrence:
>>>>>>    at MongoDB.Driver.Internal.**MongoC**onnection.SendMessage(**
>>>>>> MongoReq**uestMessage message, SafeMode safeMode)
>>>>>>     at MongoDB.Driver.**MongoCollection**.InsertBatch(**Type
>>>>>> nominalType, IEnumerable documents, MongoInsertOptions options)
>>>>>>    at MongoDB.Driver.**MongoCollection**.Insert(Type nominalType,
>>>>>> Object document, MongoInsertOptions options)
>>>>>>    at MongoDB.Driver.**MongoCollection**.Insert(Type nominalType,
>>>>>> Object document, SafeMode safeMode)
>>>>>>    at MongoDB.Driver.**MongoCollection**.Insert(Type nominalType,
>>>>>> Object document)
>>>>>>    at MongoDB.Driver.**MongoCollection**.Insert[**TNominalType](**TNominalType
>>>>>> document)

>>>>>> Our connection string has all three server names and ports as per the
>>>>>> documentation.

>>>>>> It appears as if the MongoDB Connection in the C# driver is not
>>>>>> checking that the one it knows to be primary is still the primary when
>>>>>> doing a write operation. The only way we can recover from this is to
>>>>>> restart the application pool the web application is running in, thereby
>>>>>> forcing the next request to re-create the database connection object and
>>>>>> then it knows which of the three server instance is now the primary again.

>>>>>> Is this perhaps a known issue with the version of the server software
>>>>>> and C# driver we are using? We are planning on updating the code-base to
>>>>>> use the latest version of the C# driver shortly.

>>>>>> Thanks in advance

>>>>>> Regards,
>>>>>> Demitri