Feature #3302
closedceph-disk: activate-journal, and matching udev rule
0%
Updated by Anonymous over 11 years ago
Summary: try starting the OSD again when the journal disk appears.
Currently, osd data disk add is seen in /etc/init/ceph-hotplug.conf, and then the $osd_data_dir/journal symlink is followed to find an external journal. If an external journal is not available at the time the OSD would start up, it'll fail.
Add a second upstart job definition, /etc/init/ceph-hotplug-journal.conf, that triggers on block device addition with ID_PART_ENTRY_TYPE=...ceff106, that peeks inside the journal to see the osd uuid associated, looks for a partition with that unique uuid (and type uuid=...ceff05d"), and then does "initctl emit block-device-added ..." to get /etc/init/ceph-hotplug.conf running for it.
Beware: there might be a race condition:
- ceph-hotplug: starts
- ceph-hotplug: no journal disk yet, cannot start osd, about to exit soon
- ceph-hotplug-journal: starts
- ceph-hotplug-journal: make sure ceph-hotplug is started (it is!)
- ceph-hotplug: finally stops (no osd running yet)
- ceph-hotplug-journal: stops (still no osd!)
To avoid that, ceph-hotplug-journal might need to see if ceph-hotplug is running, wait for the current instance to exit, and then start a new one?
Updated by Sage Weil about 11 years ago
- Subject changed from upstart: provide ceph-hotplug-journal that can also trigger ceph-hotplug to ceph-disk: activate-journal, and matching udev rule
- Status changed from New to 12
- Priority changed from Normal to High
Updated by Sage Weil almost 11 years ago
- Status changed from 12 to Fix Under Review
- Assignee changed from Anonymous to Sage Weil
- Priority changed from High to Urgent
this was causing unreliable ubuntu activation, at least in my case
Updated by Sage Weil almost 11 years ago
commit:a2a78e8d16db0a71b13fc15457abc5fe0091c84c
Updated by Sage Weil almost 11 years ago
- Status changed from Fix Under Review to Resolved