[SERVER-5381] MongoDB Server(ReplicaSet Secondary) remains in state 3(Recovering) after runCommand("compact") on a nonexisting collection. Created: 23/Mar/12 Updated: 24/May/12 Resolved: 24/May/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 2.0.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Guido krömer | Assignee: | Adam Comerford |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | replication | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
[root@dev-db ~]# uname -a |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
The in the summary described behavior happed on a production server, but we could reproduce ist on our development server, too. I logged in to the secondary server: Switched to hm_history database: Then started the compact command on two existing collections; RECOVERING> Until this step everyting runs fine, but after running a command on a collection wich does not exists the server remains in state recovering. Our production server remained in this state for 5 hours, so that we needed to restart the service. RECOVERING> db.dffsdfsf23422eqw.runCommand("compact") Output from rs.Status: , , |
| Comments |
| Comment by Guido krömer [ 23/May/12 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Thanks for your advices! | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Adam Comerford [ 18/May/12 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Confirmed as still happening in 2.0.5, however, subsequently running a compact on an existing collection does return the secondary to its normal stats. So, as a workaround, just run compact on an actual collection to resolve the issue.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Adam Comerford [ 17/May/12 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
FYI, testing in the 2.1.1 release, this appears to be fixed:
|