[SERVER-22941] mongoDB hangup after one or two days' high load mongoimport Created: 03/Mar/16 Updated: 08/Mar/17 Resolved: 17/Feb/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 3.2.0, 3.2.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | ??? | Assignee: | Mark Agarunov |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | WTplaybook | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
redhat |
||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
|
My server configure: I have at most 12 mongoimport process running with only one mongod instance at the same time to load data.I hava about 50 collections.And each collection has about 10 indexes. |
| Comments |
| Comment by Mark Agarunov [ 17/Jan/17 ] |
|
Hello zzz, My apologies for the delay in response. Unfortunately, we were unable to determine the root cause of the behavior described. Please note that the most recent release of MongoDB, 3.4.1, comes with many improvements which may help the issue you've observed. If this this still an problem for you, would you please upgrade to 3.4.1 and let us know if it resolves the issue? Thanks, |
| Comment by ??? [ 08/Apr/16 ] |
|
hi,Thomas, |
| Comment by ??? [ 08/Apr/16 ] |
|
hi,Thomas, ------------------ 原始邮件 ------------------ 主题: [MongoDB-JIRA] ( Thomas Schubert commented on Hi zzz, We are still investigating the diagnostic data and logs that you have provided. Can you please upload the output of db.currentOp() when you observe this issue? Please also upload the logs after the affected MongoDB receives a shutdown signal. Thank you, ---------------------- |
| Comment by Kelsey Schubert [ 07/Apr/16 ] |
|
Hi zzz, We are still investigating the diagnostic data and logs that you have provided. Can you please upload the output of db.currentOp() when you observe this issue? Please also upload the logs after the affected MongoDB receives a shutdown signal. Thank you, |
| Comment by ??? [ 23/Mar/16 ] |
|
I hava uploaded diagnostic.data and full logs through that portal. |
| Comment by Ramon Fernandez Marina [ 10/Mar/16 ] |
|
Thanks for the update. There was a similar behavior in In addition to the diagnostic.data content mentioned above, if you had a script and dataset that reproduces the behavior you describe and you could upload it that would help a lot with the investigation. Thanks, |
| Comment by ??? [ 10/Mar/16 ] |
|
Now i create three dbs in my mongoDB instance.I switch to a new db to load data every 5 minutes.Each db loads data for only 5 minutes.That means,each db works 5 minutes and sleeps 10 minutes every 15 minutes.It has worked since last Tuesday,and that question doesn't show up.I didn't not reduce write pressure.In old plan,mongoDB can work only 2 or 3 days,then it hangup. |
| Comment by Ramon Fernandez Marina [ 03/Mar/16 ] |
|
Can you please upload the contents of the diagnostic.data directory inside your dbpath and the full logs for this server from startup until you experience the hang? You can upload this data through this portal privately and securely. Please let us know when the upload of the requested information is complete so we can investigate further. Thanks, |