Bug 1272542 - [RFE] When restoring from backup using engine-backup and files is included in scope, perform sanity check on ENGINE_HEAP_MAX and ENGINE_HEAP_MIN
[RFE] When restoring from backup using engine-backup and files is included in...
Status: NEW
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Yedidyah Bar David
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2015-10-16 13:06 EDT by Allan Voss
Modified: 2017-09-28 05:41 EDT (History)
10 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Integration
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Allan Voss 2015-10-16 13:06:54 EDT
If you're restoring from backup on a system with more RAM than was available when the backup was created, then /etc/ovirt-engine/engine.conf.d/10-setup-java.conf could possibly contain conflicting values that would cause ovirt-engine to fail to run. 

In a production environment, when recovering from backup on a new system, ENGINE_HEAP_MAX="2g" was included in 10-setup-java.conf, while the initial engine-setup configuration set the ENGINE_HEAP_MIN to 4g, causing ovirt-engine to crash on startup for heap issues.

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