[SERVER-3763] when one shard goes down, mongos starts returning failure in getlasterror for all the shards, to already connected client. Created: 06/Sep/11 Updated: 11/Jul/16 Resolved: 24/Jan/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 1.8.1 |
| Fix Version/s: | 2.0.3, 2.1.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | anurag berdia | Assignee: | Eric Milkie |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Mongo version 1.8.1 on 64-bit Debian machine |
||
| Issue Links: |
|
||||||||
| Operating System: | Linux | ||||||||
| Participants: | |||||||||
| Description |
|
MongoDB with 2 shards. When both the shards are up and running, our mongo driver using MongoS At the same time if another mongo driver tries to connect to same MongoS, it |
| Comments |
| Comment by Brendan W. McAdams [ 07/Feb/12 ] |
|
Sorry, mistakingly assigned wrong ticket to myself |
| 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: 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. |
| Comment by auto [ 24/Jan/12 ] |
|
Author: {u'login': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: |
| Comment by auto [ 24/Jan/12 ] |
|
Author: {u'login': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: 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. |
| Comment by auto [ 18/Jan/12 ] |
|
Author: {u'login': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: 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. |
| Comment by Eric Milkie [ 18/Jan/12 ] |
|
I believe the previous two commits now fix the issue. |
| Comment by Greg Studer [ 18/Jan/12 ] |
|
@eric - does this actually fix the issue? |
| Comment by auto [ 17/Jan/12 ] |
|
Author: {u'login': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: |
| Comment by auto [ 16/Jan/12 ] |
|
Author: {u'login': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: 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. |
| Comment by anurag berdia [ 06/Jan/12 ] |
|
It is also there in 2.0.2. Please confirm from your end. |
| Comment by anurag berdia [ 05/Jan/12 ] |
|
The issue is still open in 2.0.1. Please check link below: Please respond, |
| Comment by Eliot Horowitz (Inactive) [ 30/Dec/11 ] |
|
this was fixed in 2.0.1, so also in 2.0.2 |
| Comment by anurag berdia [ 30/Dec/11 ] |
|
This will be fixed in version 2.1.1. right? When this version is going to be available. Right now mongo db version 2.0.2 is available. |
| Comment by auto [ 25/Oct/11 ] |
|
Author: {u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}Message: more error handling and msgs for gle |
| Comment by auto [ 17/Oct/11 ] |
|
Author: {u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}Message: test for |
| Comment by auto [ 17/Oct/11 ] |
|
Author: {u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}Message: more error handling and msgs for gle |
| Comment by Greg Studer [ 17/Oct/11 ] |
|
aff5b255dae46acd8aa462564a186c21e83ebd10 and 42d9b82e816d8de09eee3d3801abb0197c337deb |
| Comment by Eliot Horowitz (Inactive) [ 06/Sep/11 ] |
|
@tony - can you write a test to reproduce |
| Comment by Tony Hannan [ 06/Sep/11 ] |
|
I am able to reproduce this in version 2.0.0-rc0. To trigger, attempt to insert into down shard then insert into up shard. The insert succeeds but error 11002 is returned. |