mdadm checkraid cronjob runs at the same time
Bug #1815201 reported by
Wouter van Bommel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| mdadm (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
| Xenial |
New
|
Undecided
|
Unassigned | ||
| Bionic |
New
|
Undecided
|
Unassigned | ||
| Cosmic |
Won't Fix
|
Undecided
|
Unassigned | ||
| Disco |
Won't Fix
|
High
|
Unassigned | ||
Bug Description
Currently the mdadm package will install a checkraid crontab, that is the same on all installations. This is fine for a single installation, but in bigger (distributed) environments this hurts performance.
E.g. having mysql clusters on softRaid all having their arrays checked at the same moment, causes problems with availability.
An solution would / could be to add an option that will allow the date-time to be randomized. Then this option / question can be used where appropriate, while still retaining the option to have the static configuration as a default.
| tags: | added: field-medium |
| Changed in mdadm (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → High |
| tags: | added: rls-dd-incoming |
| summary: |
- crontab is fixed on specific moment + mdadm checkraid cronjob runs at the same time |
| tags: | removed: rls-dd-incoming |
| tags: | added: id-5c6596886f8e66197bce7d24 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in mdadm (Ubuntu): | |
| status: | Triaged → Fix Released |
Revision history for this message
| Steve Langasek (vorlon) wrote | #2 |
| Changed in mdadm (Ubuntu Disco): | |
| status: | Triaged → Won't Fix |
| Changed in mdadm (Ubuntu Cosmic): | |
| status: | New → Won't Fix |
To post a comment you must log in.
This bug was fixed in the package mdadm - 4.1-2ubuntu3
---------------
mdadm (4.1-2ubuntu3) eoan; urgency=medium
* Drop /etc/cron.d/mdadm and migrate to systemd mdcheck_
timer units.
* Drop /etc/cron.
timer unit.
* mdcheck_start.timer configures the mdcheck on a first sunday of the
month, with a randomized start delay of up to 24h, and runs for at
most 6h. mdcheck_
start delay of up to 12h, and continues mdcheck for at most 6h.
* mdmonitor-
up to 24h.
* One can use systemd drop-ins to change .timer units timings, set
environmental variables to decrease/increase the length of checking,
or start the checks by hand. Previously used checkarray is still
available, albeit not used by timer units.
* Above ensures that previous daily / monthly checks are performed, but
are randomized, such that performance is not as impacted across a
cluster of machines. LP: #1815201
-- Dimitri John Ledkov <email address hidden> Tue, 18 Jun 2019 16:29:44 +0100