Tuning the timeout
If you plan to process documents with a large number of pages, you might need to tune the timeout of your Document Processing engine components.
Procedure
Tuning the Document Processing engine
setup
pod If your
setup
container runs into a TimeLimitExceeded
error as
follows, it is most likely due to a setup
process timeout during the processing of
documents. DEBUG | DOVP1DB2 | ONT1 | 3410e6a0-2ef9-11ec-b630-3bf409d1188f | ibm_ca.worker.caller_base.api_server.extraction.OCRUtility | Running function: save_to_storage_wimg
| ERROR | <tenantId> | <ontology> | <transID> | celery.worker.request | Task handler raised error: TimeLimitExceeded(570,)
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/billiard/pool.py", line 684, in on_hard_timeout
raise TimeLimitExceeded(job._timeout)
billiard.exceptions.TimeLimitExceeded: TimeLimitExceeded(570,)
| ERROR | <tenantId> | <ontology> | <transID> | celery.worker.request | Hard time limit (570s) exceeded for app.ibm_ca.worker.processing.initialize_doc_processing.tasks.initialize_doc_processing[9da525e8-d86d-454f-9af0-8652e55cf430]
You can increase the process_timeout parameter of the setup
pod to solve this problem.
- See Updating script-installed deployments to update your CR YAML file.
- In your CR file, under
ca_configuration.global.setup.process_timeout
, increase the process_timeout to a higher number, for example 900 (the default is 600 seconds). For more information, see ADP Configuration parameters (ca_configuration). - The operator reconciliation loop might take up to 30 minutes or more, and the
setup
pod(s) will be restarted.