admin/raven
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2021-10-28 20:07:29 +00:00
parent f0be5948d6
commit 6755f237af
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/8.0/ayanova/docs/ay-report-busy.md
View File

@@ -1,18 +1,18 @@
# REPORTING MAXIMUM LIMIT WARNING
[UNDER CONSTRUCTION PRE-RELEASE]
Rendering reports is a very demanding process at the server involving a significant of memory and cpu cycles. In order to ensure availability of the server for all users there is a configurable limit to the number of reports that can be processed simultaneously.
Rendering reports is the single most demanding task that the AyaNova server performs involving a significant amount of memory and cpu cycles. In order to not overload the server host computer and ensure availability of the server for all users there is a (configurable) limit to the number of reports that can be processed simultaneously.
When all available "slots" for processing reports are in use you will see the maximum limit warning message:
![The server is currently at the maximum limit for processing reports, please try again shortly](img/ay-report-busy.png)
It is normal to see this message from time to time and simply resubmitting the report request again will usually return the report as expected.
If you see this message on a regular basis it may indicate the need for your AyaNova server operations manager to adjust the report rendering limit settings. They should consult the Server Operations Configuration section of this manual for guidance.
When AyaNova runs out of slots and another user requests a report it will send this warning back to that user and also initiate a process to forcibly remove any in-process reports that have gone over the configured timeout limit for a report to be processed.
If you see this message on a regular basis or large reports with a lot of pages or heavy graphics do not complete at all, it may indicate the need for your AyaNova server operations manager to adjust the report rendering limit settings. They should consult the Server Operations Configuration settings section of this manual for guidance.
## How to work around limits for large reports
A large report with a unusually high number of pages may be rejected if it's taking too long to render at the server while others are attempting to report at the same time. AyaNova will only enforce the configured time out when a report is taking up a rendering "slot" and preventing other's from being able to report. This means that there are no timeout limits as long as no other users are blocked from reporting.
A large report with a unusually high number of pages or intensive graphics may be rejected if it's taking too long to render at the server while others are attempting to report at the same time. AyaNova will only enforce the configured time out when a report is taking up a rendering "slot" and preventing others from being able to report. This means that there are no timeout limits as long as no other users are blocked from reporting.
For this reason it's recommended that long running reports that are getting bumped be instead requested at a time when few if any other users will be requesting reports to avoid potential conflict and having your long running report "bumped" out of the queue.