Skip to main content
The search cluster API allows users to connect Fusion with any existing Solr instances in a Zookeeper-managed cluster.
Cluster operations are only supported when connecting through Zookeeper.
Once the Solr cluster is registered with Fusion, requests can be proxied through Fusion to it. The possible requests include search requests, but they can also be content indexing requests, such as the content crawled with a connector. Once the searchCluster has been configured, the user can create Fusion collections that refer to the Solr collections that have been previously defined.

Background

Solr has three different approaches on how you can control visibility of new documents in search:
  • You can commit manually
  • You can rely on Solr’s autoCommit setting
  • You can specify commitWithin when adding documents
Fusion uses commitWithin to avoid relying on specific Solr side configurations. Fusion controls commitWithin on a per-collection basis so you can have multiple collections with different commit frequencies (for example, product documents can be committed more often than signals). Global setting for commitWithin:
com.lucidworks.apollo.solr.commitWithin is a global configuration property that defines default commitWithin for all documents added through Fusion. Every time you create a new collection in Fusion, per-collection commitWithin is initialized as the global default. Per-collection setting: You can either specify this property when creating collection or update it with PUT later.

Search Cluster Definition Properties

Examples

Create a new search cluster that is an existing SolrCloud cluster: REQUEST
RESPONSE
Create a ‘cluster’ that is a standalone Solr instance: REQUEST
RESPONSE
Show the status of each node of ‘mySolrCluster’: REQUEST
RESPONSE
Show the system information for one named node: REQUEST
RESPONSE