[SERVER-22316] MongoDB.Driver.WriteConcernException in specific update queries Created: 26/Jan/16 Updated: 20/Jun/16 Resolved: 20/Jun/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Rodrigo Cetera | Assignee: | Kelsey Schubert |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
OS: Ubuntu 15.04 |
||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
|
When trying to make a particular update query (query.txt) over a stored document (storage.txt) the following error appear:(error.txt)
I realized that this only happens when the query have the exact field name "size_of_raw_data" with value 512. If i change the value to 513 or 511 or whatever else, the query executes in normal way. |
| Comments |
| Comment by Kelsey Schubert [ 20/Jun/16 ] |
|
Hi kdeltared, Thanks for getting back to us with the answers to my questions. From your responses, I do not see a clear explanation for the corruption you have observed. It may have been the result of an unclean shutdown some time in the past or faulty disk drives. Unfortunately, as I mentioned previously determining the root cause of this corruption is very challenging without a reproduction. If this issue persists after you have ensured the integrity of your disk drives, please let us know and we will continue to investigate this issue. Thank you for your help, |
| Comment by Ramon Fernandez Marina [ 18/May/16 ] |
|
kdeltared, looks like your reply fell through the cracks – my apologies for that. I've reopened the ticket to take a closer look. |
| Comment by Rodrigo Cetera [ 08/Mar/16 ] |
|
Hi, sorry for the delay. Right now, we are thinking to migrate to MongoDB 3.2 with WiredTiger and make other changes like SDDs disk and raid configuration, so we are going to rebuild the DB from scratch. Anyway I will execute repairDatabase in maintenance cycle to see what happens. Thank You, |
| Comment by Ramon Fernandez Marina [ 05/Mar/16 ] |
|
kdeltared, we haven't heard back from you for some time, so I'm going to close this ticket. If this is still an issue for you please provide the information requested above by Thomas so we can investigate further. Regards, |
| Comment by Kelsey Schubert [ 02/Feb/16 ] |
|
Hi kdeltared, This assertion failure generally indicates that some or all of the data files have become corrupt in some way. It's not clear if the corruption is in the index or the data itself, and in cases like this, it's very difficult to be confident that the corruption is isolated beyond the file level. To help us understand what's going on here, I've assembled a list of routine questions about data storage and the configuration of your environment. We can use this to begin debugging the underlying issue, but beware in these sorts of situations it can be difficult to understand the cause of the corruption without a straightforward reproduction.
I would recommend a clean resync from a node that is not affected. If that is not possible, I would recommend executing repairDatabase. Additionally, please consider doing a thorough integrity check of the affected node's disk drives. If the assertion failures continue to persist, you may need to replace them. Thank you, |
| Comment by Rodrigo Cetera [ 28/Jan/16 ] |
|
Ramon, Im am using MongoDB 3.0.9 with MMAP engine. Thank you |
| Comment by Ramon Fernandez Marina [ 26/Jan/16 ] |
|
kdeltared, what version of MongoDB are you using? What indexes are defined on this collection? I imported the document from storage.txt on a MongoDB 3.2.1 instance and I was able to successfully run the query. Can you please provide more information that can help us investigate? If you have a repro script that would be even better. Thanks, |