Description of problem:
Customer has customized the Java Heap configuration of DWH and increased -Xmx form 1GB to 2GB. During Z-Stream upgrade from RHEV 3.3.2 to 3.3.3 this setting was reverted to the default, and DWH failed to start in a scale environment.
Version-Release number of selected component (if applicable):
3.3.2 to 3.3.3 Upgrade
How reproducible:
100%
Steps to Reproduce:
1. Upgrade DWH during RHEV-M upgrade
2. Check Java Heap settings for DWH
Actual results:
Heap reverts to default setting
Expected results:
User-defined heap value is retained across upgrades
How can one check the Java heap configuration mentioned in comment 0 ?
Comment 3Yedidyah Bar David
2014-07-22 12:55:56 UTC
(In reply to Petr Beňas from comment #2)
> How can one check the Java heap configuration mentioned in comment 0 ?
Scott - How did they do that? Edited [1]? I do not see any other way. Do we have an article/doc recommending to do that?
[1] /usr/share/ovirt-engine-dwh/etl/history_service.sh
Thanks!
Comment 7Julio Entrena Perez
2014-10-06 11:29:37 UTC
For reference:
In 3.3: RUN_PROPERTIES="-Xms256M -Xmx1024M" in /usr/share/ovirt-engine-dwh/history_services.sh
In 3.4: DWH_JVM_ARGS="-Xms256M -Xmx1024M" in a .conf file at /etc/ovirt-engine-dwh/ovirt-engine-dwhd.conf.d directory