AI Bridge Docker 2.0.5 doesn't allow a certain amount of metadata devices to be created

I’ve decided to switch from Kubernetes to Docker for the AI Bridge 2.0.5. It is much more stable and manageable.

I’m running into an issue though where if there are so many metadata devices created, that the recording server crashes due to some sort of SQL/error/storage issue. I have yet to confirm what is exactly the issue. But I can replicate it by adding a certain amount of meta data devices per camera and at a certain point the recording server just crashes. We have a very fast raid array attached to the server with over 1 TB of storage and 128Gbs of ram. So this isn’t associated directly with actual hardware specifications.

Yesterday (5/7/2026) we called Milestone support on this (case # MSC00088667), so there is history of the situation. The recording server was in cycle reboot until we started deleting metadata devices. We have close to 400 cameras, and each camera has a metadata device subscribed to a topic. I dumped some logs into AI - The best it could configure - “A camera driver attempted to push a video frame into a PipelineQueue<T> where either the queue itself or its target buffer was null.”

Not sure if the processing server was built that way, to handle only a certain amount of metadata devices or it is a bug, or some configuration we have to change.

Any help on this would be greatly appreciated.

Hello @Vince,

The short answer is no, AI Bridge is not designed in anyway to prevent or limit the amount of neither the metadata devices nor the metadata streams.

The logs you mention refer to the operation of the Recording Server an how it deals with devices. Since the lines you are mentioning refer to a camera pushing video but you are pushing metadata, I wonder if these are related to your metadata issue.

Do you see any logged errors from the Processing Server side? Please, share your logs if you find anything that catches your attention.

Regards,

Fer