Bug 1128800

Summary: [RFE] Local domain with low available disk space leads to a very slow host,errors on engine logs and possibly host collapse
Product: [oVirt] ovirt-engine Reporter: Ori Gofen <ogofen>
Component: RFEsAssignee: bugs <bugs>
Status: CLOSED WONTFIX QA Contact: Raz Tamir <ratamir>
Severity: medium Docs Contact:
Priority: unspecified    
Version: ---CC: acanan, amureini, bugs, gklein, rbalakri, srevivo, ykaul, ylavi
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: ylavi: ovirt-future?
ylavi: planning_ack?
ylavi: devel_ack?
ylavi: testing_ack?
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-31 13:10:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On: 679070    
Bug Blocks:    
Description Flags
vdsm+engine logs none

Description Ori Gofen 2014-08-11 14:50:26 UTC
Created attachment 925807 [details]
vdsm+engine logs

Description of problem:

a Packed local domain shouldn't be aloud on any case,it damages host's Performance and can lead to collapsion. 

After filling the local domain to almost zero free space,host became very slow.

message on UI:
"Host vdsb has less than 500 MB of free space"

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

How reproducible:

Steps to Reproduce:
1.create a local domain and fill it with disks

Actual results:
Engine throws:

2014-08-11 16:51:01,162 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-16) Correlation ID: null, Call Stack: null, Custom Event   ID: -1, Message: Critical, Low disk space. Host vdsb has less than 500 MB of free space left on: /var/log/core, /tmp, /var/log, /var/run/vdsm/.

host become's slow.

Expected results:
local domain should have a different space policy from regular sd due to the sensitivity of its location

Additional info:

Comment 1 Ori Gofen 2014-08-13 13:04:24 UTC
we can really use a threshold flag which will also block with CDA, operations who violates the space policy,not only warn the user.

for example when RPE,BZ #679070 ,will be operational (I'll refer to #679070 RFE as 'FreeSpaceCriticalLowOnDomainInGB',and to simplify,this feature will be 'FreeSpaceCriticalLowOnDomainFLAG') a user should be able to set a related flag to 'permissive' ,'enforce' . permissive will warn the user,and enforce will block with CNA the operations which violate the free space policy.

Naturally,the configuration of a local domain will be by default:


FreeSpaceCriticalLowOnDomainFLAG -> could not be changed
FreeSpaceCriticalLowOnDomainInGB -> could not be set to integer below SOME_THRESHOLD

Comment 3 Allon Mureinik 2017-01-31 13:10:24 UTC
The free space threshold can be configured per domain, we won't do anything out of the box here.