[SERVER-19004] mongos segfault with master nightly in Jenkins Created: 17/Jun/15 Updated: 05/Feb/16 Resolved: 27/Jun/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.1.4 |
| Fix Version/s: | 3.1.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bernie Hackett | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 5 06/26/16 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
Over the last few days the python driver tests have been failing against master-nightly in Jenkins when run against a sharded cluster. It's not clear what test is tickling the bug, and seems to vary from test run to test run. I'm attaching the mongos log from one run. The backtrace is:
|
| Comments |
| Comment by Kaloian Manassiev [ 29/Jun/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
|
david.golden, let me know if it went away with the latest build. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Githook User [ 27/Jun/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Bernie Hackett [ 27/Jun/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Reopening since the commit that resolved this ticket has been reverted. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Githook User [ 27/Jun/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Author: {u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'visualzhou@gmail.com'}Message: Revert " This reverts commit ce22d7ea21ad0f529b0dbb4e0b9264d1a68637ff. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Kaloian Manassiev [ 26/Jun/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Should be fixed by this commit: https://github.com/mongodb/mongo/commit/ce22d7ea21ad0f529b0dbb4e0b9264d1a68637ff | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Githook User [ 26/Jun/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: This change removes the ability to call runCommand directly through the It also special cases running commands on the config shard to go through | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Bernie Hackett [ 18/Jun/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The problem persists with the latest nightly, which includes the above commit. I'm attaching a new logfile. The backtrace looks the same:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Bernie Hackett [ 17/Jun/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
|
That was fast! I'll post back if the next nightly continues to have issues. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Githook User [ 17/Jun/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: Currently there is a discrepancy between the ownership of the targeter This change moves the ownership of targeter to the Shard object itself. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Bernie Hackett [ 17/Jun/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The command sent to mongo-orchestration to start the cluster:
|