Cambria Cluster is a scalable, transcoding network of multiple Cambria FTC machines for processing a large volume of video files. The Cambria Cluster Manager routes actions across the network.
Frequently Asked Questions
How many Cambria FTC's can it manage?
Cluster Manager can manage any number of FTC clients; however, we recommend managing up to 50 FTC clients due to our testing limits.
Does it have a full redundancy capability?
Yes, Cluster Manager offers full redundancy by allowing a Backup Manager configuration on a different machine. The database is mirrored between the Primary and Backup, ensuring no Watch Folder or Job information is lost if the Primary machine goes down.
Does it have a notification feature?
Yes, Jobs can include notification tasks such as sending Email, HTTP requests, creating Logs, and running Command Line Tasks. These tasks are triggered by events like transcoding errors, job start/finish, and upload successes/failures. String replacement variables allow you to customize the notification content.
Does it come with API?
Yes, Cluster Manager and FTC feature a REST-based API that enables you to submit, monitor, and control transcoding jobs throughout your entire Cambria Cluster.
Can it run in the cloud?
Yes, Cluster Manager and FTC can be deployed in a Kubernetes Cloud environment, leveraging redundancy features like manager replicas and auto scalers to dynamically allocate machine resources to handle peak transcoding loads.
Please provide us with your details using our contact form, and we will reach out to you personally to schedule a demo and arrange an evaluation license.
Cambria Cluster can track chargeable activity and prepares bills based on customer usage per month.
Split and Stitch
Reduce processing time while saving money. Split and Stitch separates source files into small chunks and processes them on multiple on prem or cloud computers. This flexible approach dramatically reduces compute time, and lowers costs by using cheaper spot cloud instances.
Workflow
Role Based API
Cambria Cluster's role-based API can limit control the scope of each software client to allow only specific categories of work when multiple tasks are assigned across a network. Access is controlled through tokens with various permission levels.
On Prem, In the Cloud, or Hybrid
Cambria Cluster can be installed on prem or in the cloud. Even when located on prem, it can control Cambria instances in the cloud. It can also add and manage Cambria FTC in the cloud.
Productivity
Load Balancing
Cambria Cluster manages load balancing, distributing transcoding jobs across the network.
Slot Number Setting
User can chose how many jobs to run concurrently on an individual machine. Cambria Cluster has a dynamic slot option to choose the optimal number of slots to use based on the number of jobs queued.
Machine Maintenance
Cambria Cluster can remotely reboot each Cambria FTC workstation to maintain the operational health of each system.
Fail Over, Redundancy
Cambria Cluster manages fail-over between Cambria FTC machines. If one Cambria FTC workstation fails, it automatically re-assigns jobs to other Cambria FTC machines. Cambria Cluster itself can have full redundancy when there is a Cambria Cluster backup machine.
Urgent Jobs
Labelling a time sensitive job in the queue as urgent will cause each Cambria FTC workstation to open an extra slot for transcoding. Urgent jobs run at a higher priority for maximum processing power, automatically pulling CPU resources from other operations without the need to manually pause and later resume other jobs.
Job Tag
Cambria Cluster can create job tags for individual Cambria FTC workstations so that tagged jobs will be dispatched to the correct FTC machine.
Integration
Rest Based API
Transcoding jobs and resources can be easily controlled through an API.
Prometheus
Cambria Cluster is integrated with Prometheus, making it easy for users to monitor Cambria Cluster Alerts.
Other Unique Features
Split and Stitch
Split a source file into small chunks and distribute them to multiple Cambria FTC machines. Cambria Cluster can re-assign clips to alternative machines in the case of faliure. Chunks from the original clip are then reassembled by Cambria Cluster into a single, encoded file.