[SERVER-22553] mongos_shard_failure_tolerance.js should not rely on order of shard ids Created: 19/Jan/16 Updated: 26/Apr/18 Resolved: 10/Feb/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.4, 3.3.2, 3.4.15 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Spencer Jackson | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | test-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Completed: | |||||||||
| Backport Requested: |
v3.4
|
||||||||
| Sprint: | Sharding 10 (02/19/16) | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 18 | ||||||||
| Description |
sharding_csrs_continuous_config_stepdown_WT failed on enterprise-rhel-62-64-bitmongos_shard_failure_tolerance.js - Logs | History BF Ticket Generated by spencer.jackson |
| Comments |
| Comment by Githook User [ 26/Apr/18 ] | ||||||||||||||||||||
|
Author: {'email': 'misha@mongodb.com', 'username': 'mikety', 'name': 'Misha Tyulenev'}Message: | ||||||||||||||||||||
| Comment by Githook User [ 17/Feb/16 ] | ||||||||||||||||||||
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: | ||||||||||||||||||||
| Comment by Githook User [ 10/Feb/16 ] | ||||||||||||||||||||
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: | ||||||||||||||||||||
| Comment by Kaloian Manassiev [ 10/Feb/16 ] | ||||||||||||||||||||
|
I think this is similar problem to | ||||||||||||||||||||
| Comment by Matt Cotter [ 04/Feb/16 ] | ||||||||||||||||||||
|
In both cases one of the dbs is getting shut down while a different part of the test is still trying to connecting to them.
Something similar happens in Charlie's patch build. | ||||||||||||||||||||
| Comment by Charlie Swanson [ 03/Feb/16 ] | ||||||||||||||||||||
|
Looks like it happened again in my patch build | ||||||||||||||||||||
| Comment by Spencer Jackson [ 19/Jan/16 ] | ||||||||||||||||||||
|
Huh... The error is:
From the JSTest in question, starting at line 64:
So it seems we try to make two consecutive findOne calls, and the second fails with some sort of connection refused message. Maybe this is something with networking? samantha.ritter, could you take a look at this, or forward on to someone else who might have a better idea about what's going on here? |