Skip to main content
MediaBeacon University

R3Search Cluster Manual 8.6

R3Search Cluster Manual 8.6

Introduction

R3Search is MediaBeacon’s built-in enterprise search engine. R3Search is fast, powerful, and is designed to grow with your enterprise and data set. Whenever assets are added to the system, R3Search automatically updates its search index and correlates the new asset with all other existing assets. This index of asset relationships powers the facet search, QuickSearch, Color Search, Date Search, Metrics, and other MediaBeacon search tools. 

For increased performance, especially with large data sets, R3Search can be distributed across multiple nodes, called clustering. Multiple nodes biggest benefit is having high availability. By having leader and slaves, the system can intelligently handle issues with nodes in the cluster by changing roles. With its scalable architecture, the cluster can be expanded at any time. As usage of the system and data set increases, more nodes can be added to maintain expected performance. R3Search can grow organically as needs grow, ensuring a consistent and responsive user experience across your enterprise.

When is Clustering Appropriate?

There is no defined line as to when clustering should take place. A general rule is: if a slow down during queries becomes noticeable, it may be time to consider clustering. This would normally happen on a system with millions of assets. By clustering, the index becomes distributed across multiple shards and decreases its size.

  • Was this article helpful?