Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1436161 - [RFE][scale]Increase LVs per VG alert limit
[RFE][scale]Increase LVs per VG alert limit
Status: CLOSED CURRENTRELEASE
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage (Show other bugs)
4.1.1.6
Unspecified Unspecified
unspecified Severity high (vote)
: ovirt-4.1.2
: 4.1.2
Assigned To: Tal Nisan
guy chen
: FutureFeature, Performance
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-03-27 07:04 EDT by Tal Nisan
Modified: 2017-07-31 04:42 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Release Note
Doc Text:
The recommended number of logical volumes per storage domain was increased from 300 to 1000. The alert that is issued when exceeding this number was changed to reflect that. Note that the limit will only change to 1000 if it was set to 300. If the customer manually configured the limit, the original configuration will not be overridden.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-05-23 04:13:48 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Storage
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
rule-engine: ovirt‑4.1?
rule-engine: planning_ack?
rule-engine: devel_ack+
rule-engine: testing_ack+


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 74671 master MERGED core: Change the limit of LVs per VG to 1000 2017-03-27 08:21 EDT
oVirt gerrit 74682 ovirt-engine-4.1 MERGED core: Change the limit of LVs per VG to 1000 2017-03-27 08:23 EDT

  None (edit)
Description Tal Nisan 2017-03-27 07:04:20 EDT
Description of problem:
RFE 1015186 added a limit to a number of LVs per VG (basically amount of volumes per storage domain) after which an alert will be logged after addition of another LV to the VG, the original RFE set the limit to 300 as that was the recommended limit in 3.5, currently the recommendation is a limit of 1000 per VG so the limit needs to be updated

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 guy chen 2017-05-15 06:22:40 EDT
Tested, created 500 VMS with 2 disks each on a single SD, on 501 VM creation got the expected alert.

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