Frequently Asked Questions

Following are answers to some frequently asked questions.

Which Solr version is supported?

The Solr version is compatible with 8.1.

What is the architecture?

The Solr clusters run on a single region (us-west1) on Google Cloud Platform across three zones. Each Solr cluster is supported by three ZooKeeper nodes that are not charged separately. The ZooKeeper nodes are not exposed publicly for security reasons. All Solr admin APIs except for autoscaling are exposed. (Autoscaling support is provided in Managed Search.) The Solr cluster is accessible over HTTPS behind a load balancer, and individual nodes are also reachable directly.

Are there service rate limits?

Yes. For more information, contact Customer Support.

How do we handle API versioning and are APIs backward compatible?

Read the API versioning and Compatibility rules topics.

What ETL tools do you support?

Any ETL (extract, transform, load) tool such as Logstash or Fluentd can make requests to our service, as long as the tool can be integrated with our OAuth2 client-credentials flow.

What plug-ins do you support?

For security reasons, we don’t support custom plugins at this time.

What storage options are available?

Is Solr Admin exposed?

Solr Admin APIs are exposed, but some of them will be disabled, for example, the Autoscaling API.

Which Solr APIs are supported?

Most public Solr APIs are supported. These APIs are not supported:

  • /admin/autoscaling handler

  • Extraction handler

  • Nested documents

  • Using createNodeSet and createNodeSet.shuffle parameters of the Collection Create API are not supported

  • The router.name parameter of the Collection Create API. That is, implicit routing is not supported.

  • The Core Admin API is not supported. All actions that might need to change Solr’s cluster state must happen via the Collections API.