[SERVER-28945] MongoDB load increases when updating 57k large records in one query Created: 24/Apr/17 Updated: 25/Apr/17 Resolved: 25/Apr/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.2.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | sulabh | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
MongoDB Server 3.2.8, MongoDB Java Driver 3.0.2, Linux operating system |
||
| Participants: |
| Description |
| Comments |
| Comment by Kelsey Schubert [ 25/Apr/17 ] |
|
Hi sulabh84, Thank you for clarifying that a crash did not occur. I've updated the ticket summary accordingly. Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group. See also our Technical Support page for additional support resources. Kind regards, |
| Comment by sulabh [ 25/Apr/17 ] |
|
Just got the update that there was a high load on mongo db because of the size of the Document which is been updated is high 33K and the number of documents updated are 57000. So that came to high CPU usage 700-800%. But mongoDB has not crashed but high load. This is also pointing to the storage type which is used in production. But still the 700-800% CPU usage is in question. |
| Comment by Kelsey Schubert [ 25/Apr/17 ] |
|
Hi sulabh84, I've created a secure upload portal for the log files. Files uploaded to this portal are only visible to MongoDB employees and are routinely deleted after some time. I understand that sharing log files may be a challenge. However, in order for us to better understand what is going on here, and appropriately investigate this issue, we would need to see how this mongod crashed (i.e. the backtrace) and what events preceded the crash. Thank you, |
| Comment by sulabh [ 25/Apr/17 ] |
|
Hi Ramon, It is hard to share the logs since mongoDB node is running on customer site. But what i can give as information is bouquetDetails is a sub document of Service Document and bouquetDetails is an array. So, to update entry we used to use $pull the record and then we used to have another query with $addToSet to add the new document in the array. These query happen 300 time in a sequential way and whenever this process triggered by the application we used to high spike in the mongoDB node of 700-800% of CPU utilisation. Is $pull and $addToSet are not recommended to used when the records are higher which match the query criteria? Thanks, |
| Comment by Ramon Fernandez Marina [ 24/Apr/17 ] |
|
Can you please provide the logs for the affected node from the last restart until the crash you describe? Thanks, |