Project

General

Profile

Actions

Bug #20229

closed

ceph-disk systemd unit timesout too quickly

Added by Loïc Dachary almost 7 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

When there are more than a few disks, it is likely to take longer than five minutes.

http://tracker.ceph.com/issues/18060 proposed to reduce the lock contention but it does not really help because there is another global lock within ceph-disk right after that. It effectively is a noop.

http://tracker.ceph.com/issues/18740 is a better workaround because it allows to configure the timeout without modifying the systemd unit.

It would be simpler and have no undesirable side effect to just set the timeout to a very large value. There needs to be a timeout to prevent ceph-disk from hanging forever (that was the first incentive to set a timeout). But there is no good reason to set it to a value that is less than a few hours.


Related issues 1 (0 open1 closed)

Copied to Ceph - Backport #21035: jewel: ceph-disk systemd unit timesout too quicklyResolvedNathan CutlerActions
Actions #1

Updated by Loïc Dachary almost 7 years ago

  • Status changed from 12 to Fix Under Review
Actions #2

Updated by Sage Weil almost 7 years ago

  • Status changed from Fix Under Review to 7
Actions #3

Updated by Sage Weil almost 7 years ago

  • Status changed from 7 to Resolved
Actions #4

Updated by Nathan Cutler over 6 years ago

  • Status changed from Resolved to Pending Backport
  • Backport set to jewel
Actions #5

Updated by Nathan Cutler over 6 years ago

  • Copied to Backport #21035: jewel: ceph-disk systemd unit timesout too quickly added
Actions #6

Updated by Nathan Cutler over 6 years ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF