[SERVER-10000] Can't connect to mongod when another DB is being compacted (v2.2.x) Created: 24/Jun/13 Updated: 14/Jan/14 Resolved: 25/Jun/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Concurrency, Internal Code, Querying, Shell |
| Affects Version/s: | 2.2.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kay Agahd | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
linux 64 bit |
||
| Issue Links: |
|
||||||||
| Operating System: | Linux | ||||||||
| Steps To Reproduce: | 1) compact a db |
||||||||
| Participants: | |||||||||
| Description |
|
Can't connect to mongod when another DB is being compacted (v2.2.x) Mongo's doc states out that Mongo v2.2 (and newer) allows to open another shell in order to view the current ops even though another database is being compacted: http://docs.mongodb.org/manual/reference/command/compact/ However, it seems that the whole mongod is blocked and not only the database which is being compacted. > mongo s131:27018/admin -u XXX -p XXX However, the mongo shell was blocked until the compact was terminated!
As you can see, I wanted to connect at 14:46:49. I closed the shell after some minutes because it was blocked. After compaction at 14:53:28, mongo tried to auth again and closed the connection since my shell was closed already. Should I open a bug report? How can one see the progress of compaction programmatically (means not by the log-files). My mongod version is 2.2.3. |
| Comments |
| Comment by Kay Agahd [ 05/Dec/13 ] |
|
Please reopen the task. In v2.4.6 it happened again. One can't access a database while another db is being compacted. |
| Comment by Ian Whalen (Inactive) [ 25/Jun/13 ] |
|
no problem, kay.agahd@idealo.de. just add a comment if you can reproduce. |
| Comment by Kay Agahd [ 24/Jun/13 ] |
|
My last assumption was wrong. My current compact process builds the indexes right now and I'm able to connect to the admin db. I don't know why my first attempt didn't work (see above). It would be nice to know a comprehensible explanation. You might close this issue. I'll reopen it when it happens again. |
| Comment by Kay Agahd [ 24/Jun/13 ] |
|
It might be that this only happens at the end of a compaction process (when the indexes are being rebuilt) because I tried the same operation on another node and I could connect to the admin db just after having started the compact process. If this is the case, it should at least be mentioned in the doc because rebuilding indexes might be a long task on big db's during which it won't be possible to connect and read-out the current ops. |