We have to deploy at least 10 video ingestion modules in a single server machine. When we were trying to deploy 6 of these video ingestion modules, only 5 modules are running. The sixth one is always in the pending state and SS of it is attached. The SS of the module allocation logs are also attached. We tried reducing the memory constraints to 500 MB, but it was still the same. How to solve this issue?
This seems to be happening due to your current client node have insufficient resources for the extra container. if possible, you can increase the hardware resources and storage for it to accommodate the task.
When I tried to run 6 video ingestion modules in a setup having 8 cpu cores and 16 gb RAM, it was running fine and I was not facing any issues. But when I try to run the same setup in the server machine only 5 of these video ingestion containers are deployed. The configuration of the server machine I am deploying it in is 40gb RAM and it has 6 cpu cores. Does the number of cpu cores matter while deploying this?
You can check on your current configuration of generated csl_app_spec.json file for the resources allocation for the Video Ingestion container.
The resources section describes the CPU and memory resources required by the Software Module. The sum of required resources of all Software Modules deployed on a node should not exceed the capacity of that specific node.
The value of the "CPU" attribute is in CPU milli units in the csl_app_spec.json. 1 CPU = 1000m.
You can refer to this information at [WORK_DIR]/orchestrator/docs/module.pdf in the resources section. You can modify this section for each of your VI containers to ensure it will not exceed the capacity of available CPUs on the node.
The configuration of the system we are using is that it has 40 GB RAM and 6 cpu cores. Is there any other specific system configuration that you would like to know? The value of the CPU attribute is 1000m for each 6 of the video ingestion containers, and the memory assigned to each of them is 500 MB in the resources field.
The problem with your setup that has been described previously was not able to run 6 VI containers on the same system. The error showing there is not enough CPU allocation for the requested deployment. In this case, you can manage the resource allocation for each of the deployed modules in csl_app_spec.json file as mentioned in the previous reply.
The total resources of your deployed module describe in the csl_app_spec.json should match your actual hardware resources in order to run all your module in the same system.
You can refer to the module.pdf file at [WORK_DIR]/orchestration directory.
as per the above example, you can change the CPU attributes for the Resources section to match your actual hardware resources.