[SERVER-16841] rollback could exhaust all free file handles Created: 14/Jan/15  Updated: 25/Jan/17  Resolved: 23/Sep/15

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.1.9

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Benety Goh
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-20597 Save data that is rolled back to the ... Closed
is related to SERVER-18 pair3.js test fails due to one server... Closed
is related to SERVER-15929 Verify rollback files are written wit... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: RPL A (10/09/15)
Participants:

 Description   

The rollback procedure opens a rollback file per unique namespace encountered as ops are rolled back. These files are not closed until the rollback procedure is finished.
Additionally:
If a rollback file fails to open, we simply log this fact and continue.
We're not checking for write errors to rollback files at all.



 Comments   
Comment by Githook User [ 23/Sep/15 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-16841 limit number of open files when saving deleted and updated documents to rollback directory
Branch: master
https://github.com/mongodb/mongo/commit/eed6c42c9cb068f556be9fa989c5bfe8a1b1fd03

Comment by Githook User [ 17/Sep/15 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-16841 modified rollback.js to check connections made to primary during rollback
Branch: master
https://github.com/mongodb/mongo/commit/dd4615e26dabd7ac6c2998061da004065cd3cf1a

Generated at Thu Feb 08 03:42:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.