Back to bug 1329119

Who When What Removed Added
Red Hat Bugzilla Rules Engine 2016-04-21 09:10:12 UTC Flags testing_ack? planning_ack?
Yedidyah Bar David 2016-04-21 09:25:56 UTC CC sbonazzo
Flags needinfo?(sbonazzo)
Yaniv Lavi 2016-04-27 07:50:01 UTC Keywords FutureFeature
CC ydary
Target Milestone --- ovirt-4.0.0
Summary engine-backup/engine-setup need jvm heap size recalculation [RFE][text] - At the end of restore, need to note to user to review JBoss memory allocation settings.
Flags needinfo?(sbonazzo) planning_ack? ovirt-4.0.0? planning_ack+
Red Hat Bugzilla 2016-04-27 07:50:01 UTC Doc Type Bug Fix Enhancement
Yaniv Lavi 2016-04-27 07:50:14 UTC Priority unspecified low
Severity unspecified medium
Yedidyah Bar David 2016-05-01 07:27:56 UTC Flags needinfo?(ydary)
Sandro Bonazzola 2016-05-02 09:57:42 UTC Target Milestone ovirt-4.0.0-alpha ovirt-4.0.0-beta
Pavel Stehlik 2016-05-04 07:35:03 UTC Flags needinfo?(ydary)
Yaniv Lavi 2016-05-04 07:51:23 UTC Flags needinfo?(ydary) needinfo?(ydary)
Yedidyah Bar David 2016-05-04 13:31:15 UTC Keywords FutureFeature Regression
CC rhev-integ-dev
Component Backup-Restore.Engine Services
Assignee didi sbonazzo
Summary [RFE][text] - At the end of restore, need to note to user to review JBoss memory allocation settings. Engine fails to start if machine's memory is reduced by 75%
Doc Type Enhancement Bug Fix
Yedidyah Bar David 2016-05-08 05:58:42 UTC CC didi
Flags needinfo?(ydary)
Yaniv Lavi 2016-05-08 06:11:21 UTC Flags needinfo?(ydary)
Yedidyah Bar David 2016-05-08 07:56:01 UTC Flags needinfo?(ydary)
Yaniv Lavi 2016-05-08 10:37:23 UTC Flags needinfo?(ydary)
Yaniv Lavi 2016-05-23 13:18:47 UTC Target Milestone ovirt-4.0.0-beta ovirt-4.0.0-rc
Yaniv Lavi 2016-06-02 08:24:44 UTC Target Milestone ovirt-4.0.0-rc ovirt-4.1.0
Flags ovirt-4.0.0? ovirt-4.1.0?
Pavel Stehlik 2016-07-14 06:59:13 UTC QA Contact pstehlik pkubica
Flags testing_ack? testing_ack+
Sandro Bonazzola 2016-08-02 14:52:53 UTC Assignee sbonazzo didi
Red Hat Bugzilla Rules Engine 2016-08-04 13:13:19 UTC Flags ovirt-4.1.0? ovirt-4.1.0+
Roy Golan 2016-10-27 11:04:13 UTC Keywords Performance
CC rgolan
Yaniv Lavi 2016-10-27 12:24:01 UTC Priority low high
Severity medium high
guy chen 2016-11-10 13:40:39 UTC CC guchen
Yedidyah Bar David 2016-11-14 08:27:13 UTC CC eberman
Flags needinfo?(didi)
Flags needinfo?(didi)
Sven Kieske 2016-11-29 16:41:20 UTC CC s.kieske
Yaniv Kaul 2016-12-01 14:22:04 UTC Target Milestone ovirt-4.1.0-alpha ovirt-4.1.0-beta
Yaniv Kaul 2016-12-21 13:41:24 UTC Priority high medium
Severity high medium
Sandro Bonazzola 2017-01-13 15:37:30 UTC Target Milestone ovirt-4.1.0-beta ovirt-4.1.1
Sandro Bonazzola 2017-02-22 11:13:55 UTC Target Milestone ovirt-4.1.1 ovirt-4.1.3
Yaniv Lavi 2017-02-26 16:13:23 UTC Target Milestone ovirt-4.1.3 ovirt-4.1.2
Yedidyah Bar David 2017-03-06 10:36:30 UTC Status NEW ASSIGNED
Yedidyah Bar David 2017-03-07 15:53:16 UTC Link ID oVirt gerrit 73686
Status ASSIGNED POST
Link ID oVirt gerrit 73687
Link ID oVirt gerrit 73688
Yedidyah Bar David 2017-03-07 16:01:08 UTC Flags needinfo?(sbonazzo)
Yedidyah Bar David 2017-03-07 16:01:33 UTC Flags needinfo?(rgolan)
Sandro Bonazzola 2017-03-07 16:09:21 UTC Flags needinfo?(sbonazzo)
Yedidyah Bar David 2017-04-03 12:15:08 UTC Link ID oVirt gerrit 73735
Link ID oVirt gerrit 73736
Status POST MODIFIED
Status MODIFIED POST
Yedidyah Bar David 2017-04-03 12:31:50 UTC Link ID oVirt gerrit 75054
Doc Text Cause:

On new setups, engine-setup configures the engine's jvm heap size to be 25% of available memory. This configuration value is neither changed by upgrades nor by backup/restore.

If the jvm fails due to not enough memory, this was not mentioned in the logs, so was hard to understand.

Consequence:

If the engine was set up on some machine, and later on was run with much less memory (e.g. because the machine's memory was reduced, or because it was backed up and restored to a machine with much less memory), it failed, and this failure was not explained well in the logs, so was hard to understand and debug.

Fix:

The code starting the engine was changed to add to the logs details about failure of the jvm, so this is more visible (including, but not limited to, the case of not enough memory). It was also changed to limit the jvm's heap size to 90% of available memory, and add a warning to the logs about this if needed. This can be prevented by adding a configuration file with 'ENFORCE_ENGINE_HEAP_PARAMS=true'.

Result:

The engine no longer fails to start due to not enough memory. If it does fail, the logs should make it easier to understand why it failed.
Yedidyah Bar David 2017-04-03 14:25:45 UTC Status POST MODIFIED
Status MODIFIED POST
Lev Veyde 2017-04-24 14:05:42 UTC Link ID oVirt gerrit 75080
Link ID oVirt gerrit 75085
Status POST MODIFIED
Target Release --- 4.1.2
CC lveyde
Sandro Bonazzola 2017-05-04 13:46:37 UTC Status MODIFIED ON_QA
CC rhev-integ-dev
Lukas Svaty 2017-05-11 13:52:31 UTC CC lsvaty
QA Contact pkubica lleistne
Lucie Leistnerova 2017-05-12 14:32:24 UTC Status ON_QA VERIFIED
Yedidyah Bar David 2017-05-14 10:39:56 UTC CC lleistne
Flags needinfo?(lleistne)
Lucie Leistnerova 2017-05-15 10:19:30 UTC Flags needinfo?(rgolan) needinfo?(lleistne)
Sandro Bonazzola 2017-05-23 08:21:30 UTC Status VERIFIED CLOSED
Resolution --- CURRENTRELEASE
Last Closed 2017-05-23 04:21:30 UTC

Back to bug 1329119