We have a situation where in both 22R1 and now 22R2, the reporting pods need to be restarted several times a month. Has anyone else encountered this or know what may be the cause?
When it occurs:
- We see that print jobs go into Waiting status inside IFS. No errors are seen but depending on what/how they are printing, some users get a message that the print is taking time and will be completed as a background job.
- Checking the status of the pods, no errors or bad status is shown. Everything appears fine.
- Performing a stop and then a start on the ifsapp-reporting-<id> pod immediately starts processing the jobs again.
The problem occurs mostly when we have heavier volumes (most of which are actually PDF) are being printed.
Here is what we have tried so far to resolve, which doesn’t appear to have made any difference:
- Created a dedicated “In Sequence” report message queue and message queue (instead of “In Parallel” to try to avoid contention) for the jobs being sent to the NO_PRINTOUT printer being used for the PDF prints.
- Added extra replicas for the ifsapp-reporting, ifsapp-reporting-ren and ifsapp-reporting-br pods (for a total of 2 each)
Looking for any thoughts, guidance for things to try or whether this might even be a known issue in 22R2.
Thanks in advance!
Nick
