Bug 1041539 - [RFE][swift]: Use WAL journal mode for sqlite
Summary: [RFE][swift]: Use WAL journal mode for sqlite
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/swif...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 16:51 UTC by RHOS Integration
Modified: 2015-03-19 17:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:37:48 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 16:51:38 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/swift/+spec/consider-wal-mode-sqlite.

Description:

Use PRAGMA journal=WAL (keeping synchronous=NORMAL as is in db.py already) and remove the in-house pending change log for sqlite container listing updates. The sqlite3 wal file serves a similar function except (a) read queries can use it on the fly without having to update the core database/indexes, avoiding fsync() and contention; and (b) when the wal log is merged in the "checkpoints" they still don't block readers (e.g. container listings). The might require other PRAGMA statements to avoid affecting durability of other table changes aside from the 'object' one. Also the rsync code to fix corrupt DBs would need adjustment.

Specification URL (additional information):

None


Note You need to log in before you can comment on or make changes to this bug.