[OPENDJ-5979] Server does not validate sum of memory used by JE backend caches after upgrade Created: 01/Feb/19 Updated: 08/Nov/19 Resolved: 25/Feb/19
|Component/s:||config, core apis|
|Affects Version/s:||6.5.1, 6.5.0, 7.0.0|
|Reporter:||Ondrej Fuchsik||Assignee:||Chris Ridd|
|Epic Link:||Bugs 7.0|
Found with latest 7.0.0-SNAPSHOT rev. 1db9934fae1.
This issue is same as
To reproduce the issue run following commands:
The same test works fine when OPENDJ_VERSION is 6.5.1-SNAPSHOT or 7.0.0-SNAPSHOT. From first look it looks like a missing upgrade task.
Steps to reproduce:
Last point should return rc==1 and start-ds output should looks like an example below, but the instance starts with rc==0 and the output doesn't contain message about an error.
Without upgrade and direct configuration of 7.0.0 at the beginning the return rc of last step is equal to 1 and the output is same as above example.
|Comment by Ondrej Fuchsik [ 06/Feb/19 ]|
After all I think this is not an issue. The test use profiles to setup the instance. In fact multiple profiles to have multiple backends. The issue is we upgrade from 4.0.0 (5.0.0) and the framework use a fallback to regular setup (no profiles in old version) and configure only one backend with db-cache-percent set to 50. It is obvious it can't behave same, so it's test to update.
I tried the upgrade scenario with profiles with 6.5.0 => 7.0.0 and 6.5.0 => 6.5.1 and works like it should. The only thing to consider is if je-shared-cache-enable property should be set to True or to False after upgrade. Currently the default value is True.
|Comment by Matthew Swift [ 06/Feb/19 ]|
I agree, this does sound like a surprising change in behavior. I think we should have an upgrade task that disables the shared cache. Do you agree Yannick Lecaillez?
|Comment by Yannick Lecaillez [ 06/Feb/19 ]|
I agree, we should not change behavior during upgrade.
|Comment by Ondrej Fuchsik [ 08/Feb/19 ]|
Verified with 7.0.0-SNAPSHOT rev. d934122aeb7 and I added new upgrade tests for this.
|Comment by Ondrej Fuchsik [ 25/Feb/19 ]|
There is an issue when doing upgrade from 6.5.0 (je-shared-cache-enabled default value is True) to 6.5.1. After upgrade the value of je-shared-cache-enabled is False.
When I set the value of this property to False or True before upgrade the value hasn't changed.
From my point of view, the upgrade task should has got target version 6.5.0 instead of 6.5.1.
|Comment by Ondrej Fuchsik [ 07/Mar/19 ]|
Verified last problem with 7.0.0-SNAPSHOT c092b9442f5.