[SERVER-4643] one of the shard is down Created: 06/Jan/12  Updated: 11/Jul/16  Resolved: 24/Jan/12

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.0.2
Fix Version/s: 2.0.3, 2.1.0

Type: Bug Priority: Critical - P2
Reporter: jitendra Assignee: Eric Milkie
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

linux debian


Issue Links:
Duplicate
duplicates SERVER-3763 when one shard goes down, mongos star... Closed
Operating System: ALL
Participants:

 Description   

we are using one mongos, one config server and two mongod shard server.
if one of the shard down then it give error for both shard in getlast error.



 Comments   
Comment by Eric Milkie [ 24/Jan/12 ]

Backported to 2.0.3

Comment by auto [ 24/Jan/12 ]

Author:

{u'login': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-3763 SERVER-4643 use correct connection

There were two automatic variables named "conn" in scope, with one occluding the other. I mistakenly changed the logic in my last commit, so I have now fixed it, and removed the overlapping scopes.
Branch: v2.0
https://github.com/mongodb/mongo/commit/937077b4c15b75411c661232236f3b2cae70ce81

Comment by auto [ 24/Jan/12 ]

Author:

{u'login': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-3763 SERVER-4643 catch exceptions on connect to other shards when handling multiple shard case
Branch: v2.0
https://github.com/mongodb/mongo/commit/c202889e9c3d50f3e7557ceb2b1e505b519a7955

Comment by auto [ 24/Jan/12 ]

Author:

{u'login': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-3763 SERVER-4643 avoid exceptions in getlasterror due to other shards being down

I had to move the creation of ShardConnection inside the try/catch because it is possible that it might throw a SocketException if the shard is down.
This change allows shard_gle_insert.js to pass on Windows, and may alleviate Linux failures with getLastError as well.
Branch: v2.0
https://github.com/mongodb/mongo/commit/078c791acd376d60c770c444b3fcd2f5a006baa1

Comment by auto [ 18/Jan/12 ]

Author:

{u'login': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-3763 SERVER-4643 use correct connection

There were two automatic variables named "conn" in scope, with one occluding the other. I mistakenly changed the logic in my last commit, so I have now fixed it, and removed the overlapping scopes.
Branch: master
https://github.com/mongodb/mongo/commit/826d964c31f7a96c43f0467b85ff6b23f66fad68

Comment by auto [ 17/Jan/12 ]

Author:

{u'login': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-3763 SERVER-4643 catch exceptions on connect to other shards when handling multiple shard case
Branch: master
https://github.com/mongodb/mongo/commit/8a002c30c6d6749f87c618b61d3f58d54696bb7a

Comment by auto [ 16/Jan/12 ]

Author:

{u'login': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-3763 SERVER-4643 avoid exceptions in getlasterror due to other shards being down

I had to move the creation of ShardConnection inside the try/catch because it is possible that it might throw a SocketException if the shard is down.
This change allows shard_gle_insert.js to pass on Windows, and may alleviate Linux failures with getLastError as well.
Branch: master
https://github.com/mongodb/mongo/commit/937e0d8e1afbc75ef475ec99196f1866f1c56679

Comment by Eric Milkie [ 12/Jan/12 ]

I believe this is a duplicate of SERVER-3763, is this correct?
We are actively working on SERVER-3763 to correct the problem.

Generated at Thu Feb 08 03:06:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.