[SERVER-33740] Add Evergreen task for running powercycle against mobile storage engine Created: 08/Mar/18 Updated: 29/Oct/23 Resolved: 06/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.2, 4.1.2 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Max Hirschhorn |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Backport Requested: |
v4.0
|
||||||||||||||||||||
| Sprint: | TIG 2018-08-13 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Story Points: | 2 | ||||||||||||||||||||
| Description |
|
We should create a powercycle_mobile Evergreen task that performs powercycle testing while running against the mobile storage engine. It should be as straightforward as copy the definition for the powercycle task and specifying --storageEngine=mobile in the mongod_extra_options parameter to the "run powercycle test" function, although some care would need to be taken to disable the FSM clients if we do this ticket before resolving
|
| Comments |
| Comment by Githook User [ 06/Aug/18 ] |
|
Author: {'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}Message: (cherry picked from commit ac4da362f1470d865e51cf8aa013aa4d4aaab93e) |
| Comment by Githook User [ 06/Aug/18 ] |
|
Author: {'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}Message: |
| Comment by Sulabh Mahajan [ 20/Mar/18 ] |
|
max.hirschhorn, Sorry for the late response. I had another look at the SQLite documentation, and looks like at some stage the defaults with WAL mode might have changed to PRAGMA synchronous=FULL. It needs further looking into. I agree with you that either we need to configure SQLite with PRAGMA synchronous=FULL or need to checkpoint explicitly using MobileRecoveryUnit::waitUntilDurable(). We might have to study the sync guarantees provided by the underlying hardware too, for reference : https://www.sqlite.org/howtocorrupt.html#_failure_to_sync. I agree it is worthwhile to have a powercycle test added for the mobile variants. Mobile SE doesn't have a functional "validate" at the moment. I have filed |
| Comment by Max Hirschhorn [ 08/Mar/18 ] |
|
sulabh.mahajan, after reading the https://sqlite.org/pragma.html#pragma_synchronous reference you linked in |