CURRENT STATUS Due to limitation within the dwh framework, the service pulls for file existence in order to shutdown nicely. Using file as trigger is not recommended, as it performs IO (every X seconds), file needs to be maintained during package lifecycle. SUGGESTED SOLUTION Use jvm java agent technology. Implement java agent that registers for signals (SIGHUP) and produce internal jvm event, load agent when running the java. Modify the existing file pull loop to wait for a specific event within the jvm. Alter service to use SIGHUP in order to stop java process.
Solution was simple as the dwh framework can call external java functions, so a singleton that have listener to SIGTERM signal is sufficient, 10 lines of code as replacement to directory scan in intervals.
oVirt 3.4.0 alpha has been released including the fix for this issue.
verified on ovirt-3.4.0-beta3 # service ovirt-engine-dwhd start Starting oVirt Engine Dataware House: # service ovirt-engine-dwhd start Starting oVirt Engine Dataware House: # service ovirt-engine-dwhd status ovirt-engine-dwhd (pid 18802) is running... # service ovirt-engine-dwhd stop Stopping oVirt Engine Dataware House: [ OK ] # service ovirt-engine-dwhd stop Stopping oVirt Engine Dataware House: [FAILED] # service ovirt-engine-dwhd stop Stopping oVirt Engine Dataware House: [FAILED] # service ovirt-engine-dwhd start Starting oVirt Engine Dataware House: [ OK ] # service ovirt-engine-dwhd start Starting oVirt Engine Dataware House: # service ovirt-engine-dwhd start Starting oVirt Engine Dataware House:
This is an automated message: moving to Closed CURRENT_RELEASE since oVirt 3.4.0 has been released.