- There were only 3 failures during the 72 hours test, and all these 3 happened because the 2nd PDP instance didn't
- get registered in time to the new group created, and as a result, the PdpGroup Query failed. This can be ignored,
- as it was only a matter of one missing heartbeat over a period of 24 hours.
+ There were some failures during the 72 hour stability tests. These tests were caused by the apex-pdp pods restarting
+ intermitently due to limited resources in our testing environment. The second apex instance was configured as a
+ replica of the apex-pdp pod and therefore, when it restarted, registered to the "defaultGroup" as the configuration
+ was taken from the original apex-pdp pod. This meant a manual change whenever the pods restarted to make apex-pdp-"2"
+ register with the "sampleGroup".
+ When both pods were running as expected, no errors relating to the pap functionality were observed. These errors are
+ strictly caused by the environment setup and not by pap.