[SERVER-68771] Error while update with pymongo driver Created: 12/Aug/22 Updated: 12/Aug/22 Resolved: 12/Aug/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.2.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | jipeng N/A | Assignee: | Chris Kelly |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
pymongo log
mongod.log
MongoDB version: db version v3.2.8
Linux version:{} Linux nodel4.18.0 aarch64 |
| Comments |
| Comment by Chris Kelly [ 12/Aug/22 ] |
|
Hi Jipeng, MongoDB 3.2 reached end of life in September 2018 and is no longer supported. I would recommend upgrading to 4.2+ or newer for support. The MMAPv1 storage engine was removed in 4.2. In the short term, there is a chance this could be related to corruption, and you could consider running validate on your collection to see if it turns up any issues. Here's the legacy doc reference on that for 3.2. We will be unable to provide further input until you upgrade to a supported version, however you can also ask our community for help by posting on the MongoDB Developer Community Forums. Regards, |
| Comment by jipeng N/A [ 12/Aug/22 ] |
|
We used the Pymongo driver to manage the mongodb, but recently we were suddenly unable to update the data,detailed error as above. |