[SERVER-13541] Freeze using mongo + mongodump + fsyncLock Created: 10/Apr/14 Updated: 10/Dec/14 Resolved: 29/Apr/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Tools |
| Affects Version/s: | 2.4.10 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Camille Reverdy | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | dump, fsync, mongo, mongodump, replicaset | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | 1- Set up a replica set with some data 5- open another mongo on the same server 7- try to stop mongodb process – won't stop until if force using kill -9 |
||||||||
| Participants: | |||||||||
| Description |
|
While trying to dump data from a secondary server in a replica set, I get issues using fsyncLock command + mongodump; please see Steps to reproduce. In the Log file, I have strange messages : 1-
2-
3-
Am I doing anything wrong ? |
| Comments |
| Comment by Asya Kamsky [ 11/Apr/14 ] |
|
I think you are seeing https://jira.mongodb.org/browse/SERVER-1423 - does that seem about right? Technically you don't need to fsyncLock to use mongodump - fsyncLock is needed if you are doing a file copy and want to make sure that they are flushed and not changing during the file copy. Mongodump does a query, so I'm not sure whether you technically need to use it. I believe your issue will be resolved regardless when |
| Comment by Camille Reverdy [ 10/Apr/14 ] |
|
It seems that my dump is starting before the lock has been applied, and this transition state is not stable |
| Comment by Camille Reverdy [ 10/Apr/14 ] |
|
Sorry for the formatting error, and it seems that i can't edit to correct |