Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 3.1.1
-
Fix Version/s: 3.2.0
-
Labels:None
-
Environment:
CentOS release 6.7
-
Story Points:0
-
Rank:6965
-
Sprint:2016#01
Description
Code fixing it
see branch thilaire/OP-232, we are testing it in production but unit tests still to be done
Pre-conditions
Fully capable OBM-stack splitted or in the same server.
Have a configured healthcheck user for everydomain your OBM is controlling.
Reproduction steps
start spushnik probe and monitor it.
Current behavior
- after an average time of 2 hours and 30 minutes. spushnik stops to work properly.
- It is also impossible to check the heap dump because there is not enough memory avaliable for the java runtime environment NOK
Expected behavior
- we should not have to restart spushnik every 2 hours.OK
Impacts: verify that spushnik continue to work as expected for one request
QA: should be tested with endurance tests (fix already validated in production)