Feature #9580
closedceph-disk, ceph-osd: make journal [partition] creation conditional based on osd_objectstore
0%
Description
or example, with keyvaluestore-dev ceph-disk makes a journal parititon and general screws things up. see http://article.gmane.org/gmane.comp.file-systems.ceph.user/13507
1. teach ceph-diska bout each backends and whether it needs a journal
2. add a new option about whether the journal is created (blah)
3. add a ceph-osd option to query whther the backend needs a journal, which calls into ObjectStore to ask.
3 makes the most sense IMO.
Updated by Mark Kirkwood over 9 years ago
While we are thinking about this, note that some of the keyvalue backends have facility to have their "wal" aka journal file(s) located somewhere else (only Rocksdb AFAIK). Would be good if we get this covered here too!
Updated by Sage Weil over 9 years ago
Mark Kirkwood wrote:
While we are thinking about this, note that some of the keyvalue backends have facility to have their "wal" aka journal file(s) located somewhere else (only Rocksdb AFAIK). Would be good if we get this covered here too!
Hmm, I assume they are files, though? I don't think it would map directly onto the current 'journal device' symlink (to a preallocated file or raw partition).
Updated by Samuel Just over 9 years ago
- Target version changed from 0.88 to 0.89
Updated by Samuel Just over 9 years ago
- Target version changed from 0.89 to v.91
Updated by Ian Colle over 9 years ago
- Target version changed from 0.89 to v.actually90
Updated by Samuel Just over 9 years ago
- Target version changed from v.actually90 to v.actually91
Updated by Sage Weil over 9 years ago
- Target version changed from v.actually91 to v0.92
Updated by Samuel Just about 9 years ago
- Target version changed from v0.95 to v9.0.2
Updated by Sage Weil about 9 years ago
- Status changed from New to Resolved
- Target version changed from v9.0.2 to v0.95
Updated by Loïc Dachary about 9 years ago
- Status changed from Resolved to New