Lacking BEP resources

You can understand BEP resources are lacking by the following symptom: you run OCR processing, and the results are not displayed for a long period (which is a really rare issue).

Find cause

The issue can be due to various reasons:

• Unmounted and lost BEP Agents. For details, refer to Issues related to NFS shared resources.

• Limited resource capacity. Usually, one OCR Worker instance requires 2 GB of memory and 1 CPU.

note

In Work.AI versions up to v10.2.9, as there is one v1_ocr_worker and one v2_ocr_worker, you need at least 4 GB of memory and 2 CPUs. In 10.3, the FRE11 engine (/api/v1/) is deprecated.

Resolve

First of all, take a look at your BEP cluster and check the following:

• Overall available resources

• Resources allocated to different tasks and processes

If you don't see some part of your resources, it's due to unmounted and lost BEP Agents.

If the resources are not lost but almost all allocated, and there are no free resources for running OCR Workers, try adding a new BEP Agent.

View also:

• OCR license expired

• Post-upgrade rudiments

• Database connectivity issues

• OCR how-tos