[SERVER-1719] mongos process died with splitIfShould failed: medianKey command failed Created: 01/Sep/10 Updated: 30/Mar/12 Resolved: 13/Sep/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 1.6.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Alvin Richards (Inactive) | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
ec2 / ubuntu |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
Problem: > use scaleout When I tries to re-connect to the mongos I got the following vero:scripts$ ../../software/mongodb-osx-x86_64-1.6.0/bin/mongo --port 27500 -host ec2-184-73-98-241.compute-1.amazonaws.com Looking at the node running mongos, the process was no longer running. I saw the following in the logs ed Sep 1 21:01:10 [WriteBackListener] config change: { _id: "ip-10-196-174-191-2010-09-01T21:01:10-25", server: "ip-10-196-174-191", time: new Date(1283374870915), what: "split", ns: "scaleout.blogs", details: { before: { min: { ts: 26140129 }, max: { ts: 30278795 }}, left: { min: { ts: 26140129 }, max: { ts: 27936982 }}, right: { min: { ts: 27936982 }, max: { ts: 30278795 } } } } going to retry Wed Sep 1 21:06:01 [WriteBackListener] ~ScopedDBConnection: _conn != null ", ok: 0.0 } Log from shard000 reslen:856 109ms for scaleout.blogs } Log from shard001 reslen:856 443ms reslen:856 121ms reslen:856 126ms Reproduce: Does not look like an out of disk space problem. Workaround: Business Case: |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 13/Sep/10 ] |
|
The mechanism changed a bit - so finding this exact is going to be impossible. |
| Comment by Eliot Horowitz (Inactive) [ 02/Sep/10 ] |
|
Its probably a concurrency issue with the order of doing a drop |
| Comment by Alvin Richards (Inactive) [ 02/Sep/10 ] |
|
I tried a basic repro and it did not repro. Any clues from the code that make indicate what tickled this? |
| Comment by Eliot Horowitz (Inactive) [ 02/Sep/10 ] |
|
Can you make a js test? |