You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# lvdisplay
--- Logical volume ---
LV Path /dev/openebs-ssd-0/pvc-ab10ffa5-5175-41ff-8b7e-f5d0104bb04a
LV Name pvc-ab10ffa5-5175-41ff-8b7e-f5d0104bb04a
VG Name openebs-ssd-0
LV UUID JinK3h-m6tT-KdPW-u4q4-hT3d-EQCR-uQNHMC
LV Write Access read/write
LV Creation host, time k-prod-worker-1, 2022-11-10 17:45:54 +0000
LV Status available
# open 1
LV Size 1.00 GiB
Current LE 256
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2
--- Logical volume ---
LV Path /dev/openebs-ssd-0/pvc-72f9517e-749e-4cd1-929f-8b456289d281
LV Name pvc-72f9517e-749e-4cd1-929f-8b456289d281
VG Name openebs-ssd-0
LV UUID WD7z1X-4mGk-lH26-yQCH-vOmJ-8qDR-Qdw0EJ
LV Write Access read/write
LV Creation host, time k-prod-worker-1, 2022-11-16 23:42:33 +0000
LV Status available
# open 1
LV Size 350.00 GiB
Current LE 89600
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0
A lvlscan only shows one entry for the volume
# lvscan
ACTIVE '/dev/openebs-ssd-0/pvc-ab10ffa5-5175-41ff-8b7e-f5d0104bb04a' [1.00 GiB] inherit
ACTIVE '/dev/openebs-ssd-0/pvc-72f9517e-749e-4cd1-929f-8b456289d281' [350.00 GiB] inherit
Searching for ListLVMLogicalVolume revealed, that it is currently only used for the metrics. So I propose to either dedup the results from ListLVMLogicalVolume or skip them within the loop in prometheus.
If agreed upon, I can provide a PR with a fix for this issue
The text was updated successfully, but these errors were encountered:
What steps did you take and what happened:
Prometheus is no longer able to fetch metrics from a node. Checking the logs revelead the following errors in the logs
What did you expect to happen:
Scraping of prometheus metrics working without any issue.
Anything else you would like to add:
When the logical volume is split in several Segments (in this case 2),
ListLVMLogicalVolume
will return several entries. ( https://github.com/openebs/lvm-localpv/blob/develop/pkg/lvm/lvm_util.go#L854-L867 ) and since the prometheus collector only iterates over the results ( https://github.com/openebs/lvm-localpv/blob/develop/pkg/collector/lv_collector.go#L102 ) above error is shown.Compare it with lvdisplay
A
lvlscan
only shows one entry for the volumeSimilar issue was reported for a different project - see storaged-project/libblockdev#667
Searching for
ListLVMLogicalVolume
revealed, that it is currently only used for the metrics. So I propose to either dedup the results fromListLVMLogicalVolume
or skip them within the loop in prometheus.If agreed upon, I can provide a PR with a fix for this issue
The text was updated successfully, but these errors were encountered: