[SERVER-3008] CursorTimeoutTask failure during mongos shutdown Created: 27/Apr/11 Updated: 06/Sep/11 Resolved: 06/Sep/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 1.8.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andrew R | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | mongos | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 10.04 |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
I sent the TERM signal to mongos to shut it down gracefully, and I got the following stack trace in my mongos log: Wed Apr 27 00:46:52 [mongosMain] dbexit: received signal 15 rc:0 received signal 15 Mongos did not shutdown, the process is still running after this error. Sending another TERM has no effect other than this in the log: Wed Apr 27 00:59:23 [websvr] dbexit: received signal 15 rc:0 received signal 15 |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 06/Sep/11 ] |
|
See |
| Comment by Andrew R [ 28/Apr/11 ] |
|
Another repeat of the cursor timeout stack: It's trapping signal 6 (http://en.wikipedia.org/wiki/SIGABRT). Given the nature of SIGABRT, mongos should terminate after handling the signal, but it remains running. |
| Comment by Andrew R [ 27/Apr/11 ] |
|
I also found this error on shutdown: The stack is a little different but close enough that it could be related. |
| Comment by Andrew R [ 27/Apr/11 ] |
|
I've seen this several times on different instances. Most mongos processes will stop find, but ~1/4 will hit this when I stop them all (running about 8). All I see in the logs before this is many lines like this: |