Details
-
Task
-
Resolution: Won't Do
-
L3 - Default
-
None
-
None
Description
I disabled in the scope of OPT-1626 as running the ES embedded causes a conflict as it directly depends on a log4j2-core logger, which cannot be present if log4j-to-slf4j is there which we need from optimize side for proper logging from the es transport client.
Issues notices in the test itself:
- ResilienceTestWebSocketClient just checks for a status to be present but not it's value
- also ResilienceTestWebSocketClient checks on first status received (which is right after connecting) and if the assert would check the status value it would fail without waiting for the status to reach the desired state within the timeout
AT:
- ResilienceTest is converted to an IT
- evaluate the usage of an embedded elasticsearch solution (e.g. https://github.com/allegro/embedded-elasticsearch ) that can easily started/stopped from the test setup
- the issues listed are resolved