Bug 1384899 - [RFE] Redesign dmeventd to better utilize new lvmpolld mechanism
Summary: [RFE] Redesign dmeventd to better utilize new lvmpolld mechanism
Keywords:
Status: NEW
Alias: None
Product: LVM and device-mapper
Classification: Community
Component: lvm2
Version: 2.02.166
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: XiaoNi
QA Contact: cluster-qe
URL:
Whiteboard:
Depends On:
Blocks: 2044232
TreeView+ depends on / blocked
 
Reported: 2016-10-14 10:50 UTC by Zdenek Kabelac
Modified: 2023-08-10 15:40 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:
rule-engine: lvm-technical-solution?
rule-engine: lvm-test-coverage?


Attachments (Terms of Use)

Description Zdenek Kabelac 2016-10-14 10:50:40 UTC
Description of problem:

Existing dmeventd logic uses a single lvm2 thread to process all repair commands. Idea here is the usually disasters do not happen all at the same time. However 'standalone' mirror repair may takes hours to replicate mirror image and during this time dmeventd is not able to do any other action.

Now we have lvmpolld to offload most of its work to external process and making dmeventd responsible only for quick urgent repair again and leaving long running task again being executed bug 'normal' daemons (without memlocking issues like dmeventd is using).

This should also lead to better command repair split - where only 'urgent-repair' parts are running within command context - and later i.e. mirror leg addition and resynchronization are fully under lvmpolld control.

It's important dmeventd quickly returns back to monitoring and is able to handle other incoming events.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Jonathan Earl Brassow 2019-10-23 20:45:34 UTC
see also bug 814855


Note You need to log in before you can comment on or make changes to this bug.