Feature #9580
closed
ceph-disk, ceph-osd: make journal [partition] creation conditional based on osd_objectstore
Added by Sage Weil over 9 years ago.
Updated about 9 years ago.
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.
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!
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).
- Assignee set to Haomai Wang
- Target version changed from 0.88 to 0.89
- Target version changed from 0.89 to v.91
- Target version changed from v.91 to 0.89
- Target version changed from 0.89 to v.actually90
- Target version changed from v.actually90 to v.actually91
- Target version changed from v.actually91 to v0.92
- Target version deleted (
v0.92)
- Target version set to v0.95
- Target version changed from v0.95 to v9.0.2
- Status changed from New to Resolved
- Target version changed from v9.0.2 to v0.95
- Status changed from Resolved to New
- Status changed from New to Resolved
Also available in: Atom
PDF