[SERVER-24785] backup_restore.js fails when observing FTDC interim files Created: 24/Jun/16 Updated: 20/Feb/18 Resolved: 29/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.20, 3.3.11 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Mark Benvenuto |
| Resolution: | Done | Votes: | 0 |
| Labels: | bkp | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v3.2
|
||||||||
| Sprint: | Platforms 17 (07/15/16), Platforms 18 (08/05/16) | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
The backup_restore.js tests blacklists certain lock files that should not be copied when doing a backup. That blacklist was not updated to deal with ephemeral files generated by the FTDC subsystem. Either FTDC needs to change its approach to ephemeral files, or the blacklist upon which backup_restore makes its decision needs to be updated. If the latter approach is taken, our documentation for how to perform a live system backup must be updated. |
| Comments |
| Comment by Githook User [ 20/Feb/18 ] |
|
Author: {'email': 'mark.benvenuto@mongodb.com', 'name': 'Mark Benvenuto', 'username': 'markbenvenuto'}Message: (cherry picked from commit c4fc9c165026a710809df7751f00c342b5eb27f6) |
| Comment by Githook User [ 29/Jul/16 ] |
|
Author: {u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}Message: |
| Comment by Andrew Morrow (Inactive) [ 20/Jul/16 ] |
|
mark.benvenuto and bruce.lucas - Do you have any preference among the above options? The latter two, at least to me, sound like papering over the problem, and would require that our users attempting to follow our backup procedures effectively do the same thing. On the other hand, I'm not clear on what would happen with FTDC if we disallowed it to write/rotate during the entire time we were in fsyncLock, nor is it clear to me how difficult this would be to implement. Would this effectively mean that we need to add suspend/resume functionality to FTDC? How hard would that be? |
| Comment by Mark Benvenuto [ 18/Jul/16 ] |
|
We have a few choices:
|