[SERVER-2351] Unable to killOp a repairDatabase operation Created: 12/Jan/11 Updated: 12/Jul/16 Resolved: 02/Apr/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 1.6.0 |
| Fix Version/s: | 1.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Justin Lintz | Assignee: | Aaron Staple |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
CentOS 5.4 x86_64 |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
The repairDatabase operation is unable to be killed with killOp operation, the command will appear to have been run successfully but in the currentOp list, the repairDatabase still appears and the temporary database still appears in the process of being created. The operation finally appears to get killed when it goes to start the building of the indexes. I unfortunately don't have any logs of the output from the commands at the time. I spoke with Mathias last night at the LOPSA meet up and he mentioned filing a bug report for this. |
| Comments |
| Comment by auto [ 02/Apr/11 ] |
|
Author: {u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}Message: |